Before I submit a bug report - has anyone installed iOS beta on their ipad and tried running their app which uses native.newTextField?
Mine shows up in the wrong position with the wrong orientation (rotated 90 degrees!)
Built to 6.0 GM, works fine on iPad with 5.1, problem observed only on iPad with 6.0.
[import]uid: 31041 topic_id: 31017 reply_id: 331017[/import]
Does this happen on the iOS simulator too?
Can you build the NativeKeyboard2 sample app (shipped with CoronaSDK) let us know if that shows the problem too?
Does your program support multiple orientations?
So the problem only occurs if you build the app for iOS6 and run it on an iPad with iOS6 but building for iOS5 and running on the same device works?
Thanks,
Tom [import]uid: 7559 topic_id: 31017 reply_id: 124041[/import]
Mine are not rotated (I’m a portrait only app). But they are off what looks like 64 pixels too low and 8 pixels to far to the right. In a landscape only app, compiled with the latest stable version, everything is right as well as another portrait only app compile with a older version.
So it’s does not appear to be the iPad or iOS6 since I’m running the GM seed as well.
[import]uid: 19626 topic_id: 31017 reply_id: 124046[/import]
Tom:
I am unable to reproduce the problem with NativeKeyboard2. I think the problem may involve orientation.
My app is landscape only.
Your third statement is correct - I am only able to reproduce the problem building to 6 and running on 6.
One thing to note – the “incorrect” orientation and position that I’m observing appear to be as if it is placing the control as if the device was in portrait mode (even though my app does not support portrait mode, this control seems to think it’s in portrait mode). Does this make sense?
Hope this helps -
Thanks!
Scott
[import]uid: 31041 topic_id: 31017 reply_id: 124068[/import]
Scott,
I verified the problem using a sample app and the rotation issue shows up on both native.newTextField and native.newTextBox when in landscape mode. I confirmed it by building for iOS6 and running it on the iOS iPhone5 simulator. We will look at the fix tomorrow.
Thanks for reporting this.
Tom [import]uid: 7559 topic_id: 31017 reply_id: 124113[/import]
BTW, I have a similar issue on another app that was built with (gasp!) the Unity engine. [import]uid: 64538 topic_id: 31017 reply_id: 124232[/import]
Does this happen on the iOS simulator too?
Can you build the NativeKeyboard2 sample app (shipped with CoronaSDK) let us know if that shows the problem too?
Does your program support multiple orientations?
So the problem only occurs if you build the app for iOS6 and run it on an iPad with iOS6 but building for iOS5 and running on the same device works?
Thanks,
Tom [import]uid: 7559 topic_id: 31017 reply_id: 124041[/import]
Mine are not rotated (I’m a portrait only app). But they are off what looks like 64 pixels too low and 8 pixels to far to the right. In a landscape only app, compiled with the latest stable version, everything is right as well as another portrait only app compile with a older version.
So it’s does not appear to be the iPad or iOS6 since I’m running the GM seed as well.
[import]uid: 19626 topic_id: 31017 reply_id: 124046[/import]
Tom:
I am unable to reproduce the problem with NativeKeyboard2. I think the problem may involve orientation.
My app is landscape only.
Your third statement is correct - I am only able to reproduce the problem building to 6 and running on 6.
One thing to note – the “incorrect” orientation and position that I’m observing appear to be as if it is placing the control as if the device was in portrait mode (even though my app does not support portrait mode, this control seems to think it’s in portrait mode). Does this make sense?
Hope this helps -
Thanks!
Scott
[import]uid: 31041 topic_id: 31017 reply_id: 124068[/import]
Scott,
I verified the problem using a sample app and the rotation issue shows up on both native.newTextField and native.newTextBox when in landscape mode. I confirmed it by building for iOS6 and running it on the iOS iPhone5 simulator. We will look at the fix tomorrow.
Thanks for reporting this.
Tom [import]uid: 7559 topic_id: 31017 reply_id: 124113[/import]
BTW, I have a similar issue on another app that was built with (gasp!) the Unity engine. [import]uid: 64538 topic_id: 31017 reply_id: 124232[/import]
For what it’s worth, after building with xcode 4.5 (final) installed, Corona 919, and running on an iPad with the released 6.0, this problem is no longer appearing.
Someone somewhere fixed something - Thanks whoever you are!
[import]uid: 31041 topic_id: 31017 reply_id: 124780[/import]
For what it’s worth, after building with xcode 4.5 (final) installed, Corona 919, and running on an iPad with the released 6.0, this problem is no longer appearing.
Someone somewhere fixed something - Thanks whoever you are!
[import]uid: 31041 topic_id: 31017 reply_id: 124780[/import]