We have (too) many other things on our plates right now, thats all.
When we have the time, we can revisit this use case, but in the meantime we suggested a solution that would work for you with a little effort.
In this case, you can use the calibration feature of the newEditField widget.
In the sample app, change the resolution to be the same as in your app. Then go to the calibration screen and adjust the scales as needed to have the label and text field aligned. The calibration data that you obtain from this screen, you can copy paste into…[Read more]
We just added get/set properties to the edit fields =
newEditField.text – get/set the text
newEditField.returnKey – get/set the return key on the keyboard
newEditField.inputType – get/set the keyboard type
newEditField.isSecure – get/set the input for passwords
newEditField.editMode – get/set the edit (or display) mode
Hi all, widgetstown.com was featured on Corona’s blog as “Widgetstown: where the coolest widgets can be found” http://coronalabs.com/blog/2014/04/20/from-the-forum-issue-16/
Thanks for the detailed description. Just tested it in the iPhone5 corona simulator and it worked fine. After you press Enter in the 3rd field, it correctly slides down and the yellow bar is visible.
Can you please tell me under what device/simulator you are having the issue?
I did get it, but was probably confusing with my answer – I meant we will add property getters/setters using lua metatables so the end-user will use the property name only as you requested.
Thanks for the sample screens, looking forward to them
No worries about the english, your question is perfectly formulated.
Multi line will not be possible at this time as a generic implementation – the corona display.newText and native.newTextField use different line wrapping algorithms and can’t be synchronized.
However if you do not need the editField to be swapped for a newText,…[Read more]