native.newTextField issue

Solar2D General Questions/Discussion
#21

Hey Brian, sorry for the late reply - been out sick the past few days.

Currently this is marked as an important feature request though I will see if I can get any extra info in our next meeting.

Peach :slight_smile: [import]uid: 52491 topic_id: 25859 reply_id: 109862[/import]

#22

Hello,
any update?
Thanks!
[import]uid: 94304 topic_id: 25859 reply_id: 111732[/import]

#23

The status hasn’t changed, although the new roadmap is up and is this is a feature request you may wish to post on there as well - it helps it be seen by more people be aware of it and +1 it. [import]uid: 52491 topic_id: 25859 reply_id: 111920[/import]

#24

This is not a feature request. This is a bug, and a pretty serious one as well.
The textfield is not functional on android at the moment and that should really be first priority on fixing! Instead of constantly adding functions to your director class, you should focus on fixing the showstopping bugs, like this one for instance.
[import]uid: 103182 topic_id: 25859 reply_id: 111970[/import]

#25

I had to have a chat with a member of the team who works more closely with Android than I do to confirm this so I apologize for the less than speedy reply.

Here is what I was told; “Regarding the Android text field issue, that is just the default cursor positioning for Android. We didn’t make it work that way. It’s just a native text field behavior difference between Android and iOS… and I don’t consider it a bug. Now it’s fair to say that this behavior difference should be addressed by us in the future to make Android’s text field behave more like iOS (that means overriding its default behaviors).”

I hope that clarifies why this is considered a feature request and not a bug. [import]uid: 52491 topic_id: 25859 reply_id: 112463[/import]

#26

Following this as its causing no end of grief today for me too [import]uid: 75844 topic_id: 25859 reply_id: 132708[/import]

#27

Following this as its causing no end of grief today for me too [import]uid: 75844 topic_id: 25859 reply_id: 132708[/import]

#28

I have a complex workaround which enables you to use a TextBox as TextField (e.g. single line). It only partially solves the problem as the curson in my example always ends up at the end of the text if you modify the textbox.text during typing. It has only been tested in XCode for iOS today, so I don´t know if it works for Android yet (I will test this eventually…).

You can find the code in this post:
http://developer.coronalabs.com/forum/2012/04/02/nativenewtextfield#comment-137502

Hope it solves something!

Best,
Renato
Microingress Ltd [import]uid: 141323 topic_id: 25859 reply_id: 137532[/import]

#29

I have a complex workaround which enables you to use a TextBox as TextField (e.g. single line). It only partially solves the problem as the curson in my example always ends up at the end of the text if you modify the textbox.text during typing. It has only been tested in XCode for iOS today, so I don´t know if it works for Android yet (I will test this eventually…).

You can find the code in this post:
http://developer.coronalabs.com/forum/2012/04/02/nativenewtextfield#comment-137502

Hope it solves something!

Best,
Renato
Microingress Ltd [import]uid: 141323 topic_id: 25859 reply_id: 137532[/import]