13 August 2015
Big news for the Windows Simulator!!!
Our Engineering team did something really big today. We now support the native.newTextField() and native.newTextBox() APIs on the Windows simulator. And as a side benefit Windows desktop builds will also get text fields now.
There are a couple of caveats. It does not support transparency via “alpha” or “hasBackground” properties, but as of daily build 2015.2695, you can test your input in the Windows Simulator.
Go grab the build today! https://developer.coronalabs.com/downloads/daily-builds/
Infuse Dreams
Posted at 03:47h, 14 AugustExcellent work Corona team!
lieo
Posted at 04:35h, 14 Augustyata, great update !
Larry Meadows
Posted at 08:38h, 14 AugustThat is awesome news !! I Love it!!!
Great Job guys.
Larry
Larry Meadows
Posted at 08:54h, 14 Augustdoes this mean that the native text that we add to lists are more responsive ?
I have an app i have been developing for all mobile platforms and windows lags behind the others with the scrolling lists because of the text.
thanks
Larry
Joshua Quick
Posted at 17:26h, 14 AugustLarry, are you referring to Windows Phone 8? If so, then it’s not related. This is a new feature we’ve added to the Windows desktop, which affects the Windows Corona Simulator and Win32 desktop apps.
Ed Maurina
Posted at 09:36h, 14 AugustGood job Team! Glad to see you guys got this working.
Of course Jason and I are now a little sad (not really). 🙂
Nicolas Michaud
Posted at 05:32h, 15 AugustYou are the best.
Thank you
Nick
pasidaips
Posted at 19:06h, 20 Augustwohoo that is something awesome, seriously 😀 was doing app with basically textfields like 2 months ago and it took me considerable time to do it due to having to do extra irrelevant work… thanks!
RuneW
Posted at 22:57h, 20 AugustGreat news of course. But to be honest, this should have been supported from day one.
Ming
Posted at 05:16h, 21 AugustCool!!
One problem here. I can’t change my text field’s font and font size and all. eg. I use
myField = native.newTextField(160, 300, 200, 50)
myField.fontSize = 15
But no difference with
myField = native.newTextField(160, 300, 200, 50)
myField.fontSize = 3
Any guide on it?
Ming
Posted at 05:29h, 21 AugustOops. Just realized that I need to use “.size” instead of “.fontSize”. Sorry!
Ming
Posted at 05:26h, 21 AugustAlso, the position of my textfield differs in composer and non-composer app.
In non-composer app:
myField = native.newTextField(w/2, h/2, 100, 30)
the text field appears to be in the center.
In composer app:
myField = native.newTextField(w/2, h/2, 100, 30)
the text field appears to be in the bottom right corner. In order to make it center, I need to use:
myField = native.newTextField(w/4, h/4, 100, 30)
Please fix this bug! And for sure, thank you for making it testable in Windows Simulator.
Ming
Ming
Posted at 06:25h, 21 Augustokay there was a little prob in my config.lua and I’ve changed it. everything is fine now!
Ming
Posted at 06:31h, 21 Augustsorry for the spam. There is one more problem that I found after the update. My text font got all the same.
For instance, I got 10 lines of text, all using display.newText
All are “Arial”
When line 5 is “Arial Bold”, line 6 onwards changed to Arial Bold as well.
Same thing happens when line 2 is bold, line 2 onwards is bold
tnismmile
Posted at 03:05h, 22 Augustgreat update !
Rob Vermeulen
Posted at 14:26h, 22 Augustthis made my day! But why on earth did it take so long to support this?
Joan
Posted at 09:01h, 24 AugustNice one!