I’m also pondering how to simply/elegantly tackle the “create a different dummy native image” for each platform…
How did you get along and anything to share?
G
Hi G,
I created a helper “class” that enables me to create the native TextField, the dummy text field, and the dummy text with one call to my “class” method. The “class” also handles the visibility of the dummy text field and text on the focus events and the removal of the native object after transitioning.
It works well except I don’t like the apparent contrast between the native TextField and the dummy text field and text when viewed on the actual device. I am played around with using an image that simulates the native TextField for a specific device but I can still see the change. Trying to position and size the dummy text to match perfectly with the text in the native TextField was a headache.
So in one project (a business app) I altered the UX design of the screen to show only the dummy text and NOT the dummy text field when the native TextField has no focus and is invisible. When the native TextField loses focus a transition is done to fade it away and fade in the matching dummy text.
In another project (a game app) I do not use any native objects. I simulate the TextFiled. It looks like a stylized command-line text entry (complete with blinking vertical mouse cursor). That one took some time to pull off.
I’ve been very busy making deadlines for a few important projects including a video course on Corona SDK. I will try to carve out a little time in between to post my experience and code soon.
Theo
Thanks - I’d really like to see a quick example of that business app where you fade in/out a dummy text field to see how viable this approach is… most seem to suggest it isn’t and looks aweful.
This is where I wish Corona focused more on getting this stuff right and less on adding more features when the existing features are sub optimal.