Interesting but even if it is a bug, I’d be happy if Xojo ignored it.
I cant recall anyone else wanting to call a control ‘textarea’ or ‘listbox’
Is there a real need for this, or does it reveal a more general issue about accented characters in the Unicode range?
I do not recall why I set leading Emojis to these (seven or more) PushButtons, but when I wanted to remove them (without loosing them, so I pasted the Caption into a text file), I discovered this.
BTW: I may be wrong on my text no, but
I was talking about the PushButton Caption, not Control Name.
A Control Name with a leading emoji beurk (but, after all, if someone want it ).
I would have no problem if Xojo allowed Emoji characters in anything “string” (OH! sorry… “text”) related… including captions and other control labels.
I have using special unicode character symbols many times without incident… so why not an Emoji?
Now one place where I would NOT consider this appropriate is in field, control and variable names. Something that SWIFT not only allows but touts as a feature! It destroys readabilty… seriously what does = 5 really mean?
we already do (have for quite some time)
it cannot be the first character - that has to be ascii [a-zA-Z] and after that you can use just about anything
of course you cant use things like +(). in the name
try it