native.newTextField bug?

Solar2D General Questions/Discussion
#1

Just noticed this a moment ago when testing my application on my device. When transitioning to a page with a native.newTextField element, it displays intermittently at position (0, 0) for a fraction of a second before moving to its designated coordinates. I’m not sure if this is a bug with a new test build as I haven’t changed this portion of the code in a while but it’s the first time I’ve noticed this. I was unable to trigger this in the simulator but on the device it triggers roughly 70% of the time.

Anybody else notice this behavior? [import]uid: 85128 topic_id: 25755 reply_id: 325755[/import]

#2

I do.

When going for the “scene” that they`re placed into, YES, i am able to see, when running on iDevice, that the textFields do “travel” from position [lua]X=0; y=0[/lua] to the position I hard-coded into the .lua file.

PS: I`s a matter of miliseconds I think but my perception is still getting it.

PS: Also does not matter changing the FPS from 30 to 60 by the way.

PS3: The issue is not a show stopper anyway, it is just a “sinister” effect - looking like a “bad” coded/built app or a false native view/code. :\

Just my thoughts,

Rodrigo. [import]uid: 89165 topic_id: 25755 reply_id: 104140[/import]

#3

Thanks Rodrigo. Glad to know that it’s not just me. Has anybody found a workaround for this? [import]uid: 85128 topic_id: 25755 reply_id: 104146[/import]

#4

@mew002, No Problem.

By the way, as you have started the topic asking for a workaround for this issue, am going in the same boat wishing to have a answer too.
Cheers,
Rodrigo. [import]uid: 89165 topic_id: 25755 reply_id: 104147[/import]

#5

Hey Rodrigo I’ve gone ahead and submitted a bug report since I can’t think of a workaround for this issue. I’ll let you know if there’s any good news. [import]uid: 85128 topic_id: 25755 reply_id: 104584[/import]

#6

Hey @mew002 , thank you very much for that and be sure that I`ll be waiting for “hearing” something from you here.
Cheers,
Rodrigo. [import]uid: 89165 topic_id: 25755 reply_id: 104585[/import]

#7

Hey Rodrigo I seem to have found a workaround. When creating the display elements initially set them to alpha = 0 or isVisible = false. When you transition them onto the screen create another quick transition right above it setting alpha = 1 with time = 0 or just set it isVisible = true. For the record I’m adjusting the alpha and I haven’t noticed the bug yet. Hope that helps :). [import]uid: 85128 topic_id: 25755 reply_id: 105839[/import]

#8

@mew002 ,

Thank you for that really! Sure using the property [lua]object.isVisible[/lua] would be a “nice” workaround regarding this “bug” for sure, I can imagine already. :slight_smile:

Hey, really glad by your reply.

Thanks for that,
Rodrigo. [import]uid: 89165 topic_id: 25755 reply_id: 105842[/import]