native.newTextField is still broken!? two videos showing how:

Solar2D Daily Builds and Public Releases
#1

This is how native.newTextField used to work in SDK Version 2.0.0 (2010.9.16.148):

http://www.youtube.com/watch?v=Crftsp7keMQ
And this is how it’s broken in that last two versions of the SDK. This is the latest SDK Version 2011.268 (2011.1.20):

http://www.youtube.com/watch?v=817zLJ6963M
Man. This has got to get fixed. Until it is fixed I’m sticking with SDK 148.

Also I can’t believe that no one is loudly complaining. Doesn’t anyone use native.newTextField ? [import]uid: 295 topic_id: 5852 reply_id: 305852[/import]

#2

This has to do with assigning native.newTextField to a group, the same group as the options screen, so that the native.newTextField is/isn’t displayed (transitioned in/out) along with the options screen.

I posted about this at least a month ago but I can’t find my post. Even searching for my user name ‘TokyoDan’ doesn’t return that post. [import]uid: 295 topic_id: 5852 reply_id: 20033[/import]

#3

watching the 2 videos i couldn’t believe it

people do not complain for various reasons. the most obvious is that they haven’t found out yet. i do use text fields, yet i didn’t know before reading your post

why do you want to put a native text field in a group, since it doesn’t inherit display group properties?

i was looking for some posts of mine, and couldn’t find them either
how about searching your mail regarding forum posts?

[import]uid: 6459 topic_id: 5852 reply_id: 20467[/import]

#4

Well the native text fields used to be OK in groups in the SDK two versions ago. Why were they OK in groups then but not in the last two SDK releases? Just the fact that they worked in groups two versions ago proves that it is possible.

If you can’t put native text fields in groups it means they are almost useless except in the most simple toyish apps that have only one screen. Of course you could hide/show the native text fields at the appropriate times but it’d be a big pain in the butt to achieve the nice scroll up with keyboard effect that I had in the first video.

I don’t keep all the email I get regarding my forum posts. I delete them as soon as I read them. Thanks for the suggestion though. [import]uid: 295 topic_id: 5852 reply_id: 20487[/import]

#5

I am also having this same problem and it is making working with native objects a complete pain. Any updates on how/when/if this could be solved would be great. [import]uid: 5833 topic_id: 5852 reply_id: 21999[/import]

#6

I have tried all solutions posted in the forums like object:removeSelf(), object.isVisible = false, moving it off the screen(ie: object.x = 500), I even made sure I had the latest ui.lua library which it’s ver. 1.5, but nothing seems to work.

I upgraded to the latest daily build Version 2011.268 (2011.1.20) hoping it was fixed, but the issue is still there.

It was supposed to be reported as bug #301, but searching the bug database it’s gone…

Ansca please help us, this has been documented several times in the forums. I love Corona but this is driving me crazy…Thanks in Advance. [import]uid: 9546 topic_id: 5852 reply_id: 28649[/import]

#7

+1

Ansca please…

-FrankS.
[import]uid: 8093 topic_id: 5852 reply_id: 28664[/import]

#8

This is a bad bug, I agree. We are working on a fix presently. Thanks for your continued patience.

Tim [import]uid: 8196 topic_id: 5852 reply_id: 28823[/import]

#9

Bump… [import]uid: 8093 topic_id: 5852 reply_id: 30628[/import]

#10

Bump… will this be fixed for the upcoming release…? [import]uid: 8093 topic_id: 5852 reply_id: 31715[/import]

#11

I start evaluating Corona SDK and stuck on text field for one day. I read all the docs and thought I made some mistakes until I read the post. [import]uid: 36276 topic_id: 5852 reply_id: 33231[/import]

#12

any status on this one?? [import]uid: 6175 topic_id: 5852 reply_id: 34841[/import]