Just installed daily build 2014.2329 and noticed that the iPad (non-retina) Simulator is “cut” almost in its half.
I would post here a screenshot but this Forum doesn’t allow to post any file above 8kb… 
Update: After restarting Corona, it came back to normal
I run into this pretty frequently too - restarting Corona always does the trick but anyone know why this happens?
Do you use 2 monitors?
yeah I do
Me too. I noticed the the simulator only appears broken on my second monitor and usually when it loads in a way that it has part of it outside of monitor.
But you know, has been a while since it happened to me.
yeah - I think you may be right about the split. Here’s a screenshot for the corona team
We found an issue with the simulator skin being cut off on OSX 10.9.4 when running the skin on the secondary monitor. It seems to occur when you switch from Portrait to Landscape and back to Portrait. Rotating the skin in the simulator seems to correct it. Also moving the skin to the primary monitor (and reloading) fixes the issue.
If you uncheck “Display as separate spaces” in the Mission Control Settings, this problem goes away.
There is a pending bug case on this issue.
I run into this pretty frequently too - restarting Corona always does the trick but anyone know why this happens?
Do you use 2 monitors?
yeah I do
Me too. I noticed the the simulator only appears broken on my second monitor and usually when it loads in a way that it has part of it outside of monitor.
But you know, has been a while since it happened to me.
yeah - I think you may be right about the split. Here’s a screenshot for the corona team
We found an issue with the simulator skin being cut off on OSX 10.9.4 when running the skin on the secondary monitor. It seems to occur when you switch from Portrait to Landscape and back to Portrait. Rotating the skin in the simulator seems to correct it. Also moving the skin to the primary monitor (and reloading) fixes the issue.
If you uncheck “Display as separate spaces” in the Mission Control Settings, this problem goes away.
There is a pending bug case on this issue.
