Which characters CANNOT be entered in llTextbox?

[jak Scribe]

I am using Linkset to store my data and I need a separater inside the Linkset-Key to separate a Group name from a Texture name. ie: "Animations<separator>Texturename".

The HUD-User can enter thier own Groupnames using llTextbox, therefore I need a separater that cannot be entered as part of the entered text.

 

Any ideas out there?

[Quistess Alpha]

As far as  know, they can enter anything they want. If it were me, I'd use a 'zero-width space' as the separator. https://en.wikipedia.org/wiki/Zero-width_space

ETA: Apparently, the forum software does not like ZWSP's. Now that we have llChar, you could just use llChar(0x200B);

Edited February 11, 2023 by Quistess Alpha

[jak Scribe]

Thank you Tessa, I will try it out 👍

[jak Scribe]

I tried the following:

string  seperater = llChar(0x200B);

and get a Syntax error

Do I need to create an llOrd(value, index) first?

If so what value and index must I use?

[Quistess Alpha]

6 hours ago, jak Scribe said:

I tried the following:

string  seperater = llChar(0x200B);

and get a Syntax error

Is it in state_entry()? function calls aren't allowed outside an event.

Edited February 13, 2023 by Quistess Alpha

[jak Scribe]

No it is not inside a Function.  I tried it as the initial variable definition.

[jak Scribe]

But you confused me?  I use Function calls everywhere.

[Frionil Fang]

Function calls are not allowed in the global section, only in events or functions.

You have to do this instead:

string separator;

default {
  state_entry() {
    separator = llChar(0x200B);
  }
}

Or alternatively, you could copy that character from some tool like https://unicode-table.com/en/200B/, and just paste it as a string literal in the global section:

string separator = "";

(yes, that actually contains the character, but since it's a zero-width space it's invisible)

[Quistess Alpha]

5 hours ago, Frionil Fang said:

(yes, that actually contains the character, but since it's a zero-width space it's invisible)

actually forum software deletes it, or at least I was able to copy the character from Wikipedia but not Invision forums.

[Frionil Fang]

Looks like it, can't get it back from between the quotes either. At least there's plenty of sites offering direct "copy character" buttons so you can be sure you got it.

[primerib1]

On 2/12/2023 at 1:08 AM, jak Scribe said:

I am using Linkset to store my data and I need a separater inside the Linkset-Key to separate a Group name from a Texture name. ie: "Animations<separator>Texturename".

The HUD-User can enter thier own Groupnames using llTextbox, therefore I need a separater that cannot be entered as part of the entered text.

 

Any ideas out there?

Are the "Animations" and "Texturename" parts referring to names of items in inventory?

Then you can just use any character not allowed in an inventory names, such as "\n".

[jak Scribe]

The Texturename is an item name in the Inventory.

My problem is more with the "Animations".  That is just a Groupname that a user can decide on when entering textures, and it is entered in a Textbox, meaning they could use any characters they wanted.

I could of course check for a certain character and if it is there, ask the user to type in another Groupname without this character, but I wanted to keep it as user friendly and simple as possible.

[primerib1]

8 hours ago, jak Scribe said:

The Texturename is an item name in the Inventory.

My problem is more with the "Animations".  That is just a Groupname that a user can decide on when entering textures, and it is entered in a Textbox, meaning they could use any characters they wanted.

I could of course check for a certain character and if it is there, ask the user to type in another Groupname without this character, but I wanted to keep it as user friendly and simple as possible.

Ah, makes sense.

To the best of my knowledge, U+0009 (HT = Horizontal Tab) character cannot be typed into an llTextBox (pressing the Tab key will instead move the focus to the Submit button), and U+0009 has been tested to be safe according to BUG-233015.

Unfortunately, "\t" gets converted to "    " (four spaces) instead of U+0009, so you're not really saving much effort with U+0009 (still need to use save llChar(9) to a variable -- use local variable when needed!)

(Though you do save 1 byte in LSD as U+0009 uses 1 byte in UTF-8 while U+200B uses 2 bytes. Might or might not be significant for your use case.)