Simply put, I have an app using storyboard and widget.newScrollView. If I run the app on a device with a software key array (i.e.: Nexus 7) the Y origin shifts downward by a small amount (some value less between 10 and 30) The problem affects all scenes.
I’m using 1262 - the last G1.0 build.
Is there an adjusted variable I should be using instead of simply zero?
Fixed by using the bleeding edge, latest config.lua method! The original method had some problems.
Does your app support both portrait and landscape orientations? If so, then what you’ll notice is that an Android tablet’s bottom navigation bar moves with the app when changing orientation. This causes your app window to be resized, the aspect ratio to change, and the content scaling to change. In this case, I recommend that you use Corona’s “resize” event to re-layout your app.
http://docs.coronalabs.com/api/event/resize/index.html
Even if your app has a fixed orientation (say, only portrait) some Android tablets, such as the Nook HD, have a nasty habit of quickly resizing your app window vertically when returning from the screenlock.
Good things to remember Joshua; luckily my exact problem was issues with config.lua calculating screen size.
(Simply put, Corona does not mask any area uncovered, so if you screw up in config.lua screen calculations, you still have the full screen accessible. It just won’t obey the coordinates you expect.)
That Nook issue is a good one to remember though…
Oh, I see. Yeah, we give developers the ability to render to the letterbox area on purpose. The reason is that some app stores, such as Barnes&Noble, have been known to reject apps having black letterbox bars. So, the solution is to give developers the ability render content in that area, such as a frame or background.
Fixed by using the bleeding edge, latest config.lua method! The original method had some problems.
Does your app support both portrait and landscape orientations? If so, then what you’ll notice is that an Android tablet’s bottom navigation bar moves with the app when changing orientation. This causes your app window to be resized, the aspect ratio to change, and the content scaling to change. In this case, I recommend that you use Corona’s “resize” event to re-layout your app.
http://docs.coronalabs.com/api/event/resize/index.html
Even if your app has a fixed orientation (say, only portrait) some Android tablets, such as the Nook HD, have a nasty habit of quickly resizing your app window vertically when returning from the screenlock.
Good things to remember Joshua; luckily my exact problem was issues with config.lua calculating screen size.
(Simply put, Corona does not mask any area uncovered, so if you screw up in config.lua screen calculations, you still have the full screen accessible. It just won’t obey the coordinates you expect.)
That Nook issue is a good one to remember though…
Oh, I see. Yeah, we give developers the ability to render to the letterbox area on purpose. The reason is that some app stores, such as Barnes&Noble, have been known to reject apps having black letterbox bars. So, the solution is to give developers the ability render content in that area, such as a frame or background.