UDP "#" doesn't work when trying to change database field labels

<U1> $ patch #

then

<U1> $ clear_cmd Text1 label labeltexthere #

then

<U1> $ live #

_____

Expected result: Text1's field name is changed to labeltexthere

Actual result: Nothing happens. If I disable the "live" step (3), U1's command line is still waiting for an "enter" with the onscreen keyboard pulled up and doesn't seem to register the # at the end of the second string there

Have tried putting the text in quotes but that yields the same results. \r instead of # also yields the same result. Note that # works for me for literally everything else except this particular command.

Any ideas?

0 Druuka over 6 years ago

Are you tied to doing this over UDP strings? I don't think entering text is part of the spec for UDP strings implementation.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mikewoodld over 6 years ago in reply to Druuka

For now, yes, I'm locked to UDP - all other text I can label/edit via UDP strings other than this, including sending the actual contents of the patch database fields. It's just the changing of the field names themselves. I can get the names to go in, I just can't get that last "enter" key to send (again, ONLY in this instance )
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Druuka over 6 years ago in reply to mikewoodld

ok weird but ok. Hopefully the development team will take a look and see why the return/enter is not working in this circumstance.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel