Beta 4 - Simulator Broken for Landscape Orientations with Fixed Content build.settings

Solar2D Daily Builds and Public Releases
#1

Okay, so after correcting for the LandscapeLeft/Right fix, I find that the simulator is broken for correctly displaying orientation changes when utilizing a fixed content (i.e. letting me handle rotations for my content).

A primary point here is this code does work on the iphone without issue. The simulator is the broken piece and this bug entry.

The conversion, for me, between b3 and b4 was swapping my x,y coords for left and right as well as my rotations (90 vs 270)… this was due to the fix of LandscapeLeft vs LandscapeRight.

I apologize for the “complexity” of my code, but I am simply stripping down to a bare bones example case from my existing iPad project.

I can also add, thankfully, the alert dialogs all orient correctly now!! YAY!! :slight_smile: :slight_smile:

You can find my “AlertTest” package at:

http://spowers.net/Corona/AlertTest/

This includes some screen shots of what the b3 and b4 simulators look like.

I would ask this bug be addressed ASAP as it makes any testing in landscape for b4 for my current primary development arduous at best (as I have to build every time).

Scott
[import]uid: 5659 topic_id: 1065 reply_id: 301065[/import]

#2

Looks like the “content” setting isn’t working right in the simulator. The behavior on device is correct.

If I understand your case, you should be able to continue testing by removing all the “supported” orientations in build.settings besides “portrait”. That will lock the Corona content in the simulator to portrait mode, allowing your manual rotation to work without interference from the auto-rotation. Then you can put the settings back when you build for device.

Logged as bug #218 – thanks for the test code! [import]uid: 3007 topic_id: 1065 reply_id: 2628[/import]

#3

Thanks for the quick turnaround and the workaround.

The workaround does work for the simulator with my real app. :slight_smile:

Thanks!

Scott

P.S. To be clear, this is no longer a work breaking priority with the workaround. :slight_smile: [import]uid: 5659 topic_id: 1065 reply_id: 2637[/import]