About colors in textfield, I implemented my tagging proposal so tags are introduced by an ESC ascii code (code 27, or '\e') and contains style parameters surrounded by brackets. Style parameters are key value pairs with equal sign between them, or simply key if no value is expected or relevant, and several parameters can go into the same tag.Generic format is:

\e[key=value,key2=value2,key3,etc]

Currently only 'color' is recognized, and expect a value starting with '#' in the form #rgb, #rgba, #rrggbb or #rrggbbaa. Any other value imply using the default text color.

Not sure if hgy29 saw my update to the above message, so posting a new one.

Update after use -1. The font spacing works perfectly now. Thanks!2. Minor Annoyance - In the Gideros editor (windows). I used to be able to hit Ctrl+R to send to the player. Now I have to type F5, then Ctrl+R immediately afterward. I think you wanted to make it Ctrl+R OR F5, but currently it expects both to be typed in sequence.3. iOS player - When compiling the player in xcode, I had to comment out "frameBufferDirty=TRUE" since it was undefined. Then it compiled just fine.4. I'll soon be testing it on my iPhone X and will provide any feedback if something comes up. FYI, we have to add an iPhone sized splash image in order for the iPhone to load the app in full iPhone X mode (versus the pre-iPhone X compatible mode).

Saw it yes. Quick question about 3. is this with a player exported from the studio or the player sources in Players folder ?

EDIT: it would have been with the one in Players folder, which is somehwat lagging behind in functionnalities. I will remove that line in the code but I think it should be removed completely at some point, since on can export a custom player with appropriate plugins from the studio anyway.

EDIT 2: For 2. Yes thats what I meant. It looks like it doesn't work the way I thought, will fix this.

About iPhone X support. Three changes have been made in Gideros to support it:- DPI is correctly reported for this new model- Full screen can be enabled through 'require' plugin- the display safe area (area not obscured by the top notch, rounded corners or apple on screen controls for gestures) can be queried by application:getDeviceSafeArea()

Ahhh that must because the fullscreen mode isn't enabled then. I should just return the logical bounds in that case, because iOS limits your app to the safe area anyway (compatibility mode) if you don't enable fullscreen mode, so insets are irrelevants. I didn't try that case, that's true.