Regarding the issue with textFields not transitioning properly, that’s a known bug I assume as I reported it last year but it hasn’t been fixed yet. What I am currently doing to transition textFields is load in a fake textfield image and delete the real one, then just transition the image instead. It’s a messy workaround but does the trick. Btw the bug report id is #15926 [import]uid: 14018 topic_id: 36262 reply_id: 144074[/import]
I’m using director, not storyboard. Also, even when I remain within the same page, I can’t kill the native text field.
(I tried removing it once the entry has been made, but nothing happens.)
The duplicate appears when I try to move the original native text field. [import]uid: 77043 topic_id: 36262 reply_id: 144081[/import]
Mitaten, thanks for pointing out the bug submission. My issue is that I can’t even kill the original field. If I could do that, I’d be fine. [import]uid: 77043 topic_id: 36262 reply_id: 144084[/import]
How do you create the field? Perhaps it’s a reference issue? Got some code to paste? [import]uid: 14018 topic_id: 36262 reply_id: 144185[/import]
sure, here’s how I create my field:
local textFont = native.newFont( native.systemFont )
local currentTop = sbHeight+tbHeight+shadow.contentHeight+10
local padding = 10
titleField = native.newTextField( padding, 5, display.contentWidth-(padding\*14), 80 )
titleField.font = textFont
titleField.size = 50 Again, this is outside any function or for loop, so it should only be called once.
For the time being I’m using a rigged faux text field, but I’m not crazy about it. Artificial keyboard and the textfield itself feel…cheap? compared to the feel of the native textfield/keyboard.
I guess I could dress up my faux field to make it act like the native field, but it’s a lot of work to do something that should be easy. [import]uid: 77043 topic_id: 36262 reply_id: 144195[/import]