Currently Being ModeratedOct 26, 2013 9:03 AM (in response to kb8wfh)
Update: I can not get out of full screen mode. When it is and a bug occurs like above, I hit hit F to take it out of full screen mode. The menu bar at the top disappears when it leaves full screen move and won't come back. If I selectany thing on the Aperture application, (like a project folder), the entire screen goes dark again and jumps back into full screen mode where the entire thing is unresponsive. I have to kill it off with Force Quict and start again, although it always happens a few minutes later.
Is this a mission control/spaces issue? Or just something I need to stay out of full screen mode and wait for a bug fit fix?
Currently Being ModeratedOct 26, 2013 9:12 AM (in response to kb8wfh)
There is a new setting in Mission Controll Displays have seperate spaces. It is on by default. You can try turning it off and see if it makes any difference.
There have been other reports for other apps that multi-display is still not there yet.
Post back if you try it.
Currently Being ModeratedOct 27, 2013 2:01 PM (in response to firstlaunch)
I did try it and it somewhat changes the problem, but it is still there. The full screen system seems to get messed up and when it does, it can't seem to get out of it totally. When it starts singing daisy in full screen mode and you get it to exit full screen mode, the top menu disappears and selecting anything (even empty gray space) within the app sends it back into full screen mode, but once here, nothing responds to user action (can't select images from the browser, the HUD is unresponsive, etc). A few other quirks I can't nail down with any consistency.
The only way I have found to avoid it is to completely exit the application, reboot, restart it and never go into full screen mode. It's still a little more sluggish that it should be, but at least I can do my work and get things to clients. Entering full screen mode just seems to be too buggy for practical purposes so far.
Currently Being ModeratedOct 27, 2013 6:06 PM (in response to firstlaunch)
I'll give it a try. The problem does not happen every time and doesn't start the moment you go into Full Screen mode. I was in it for about 45 minutes the last time before it hit. It's very intermittent which makes it notoriously hard to reproduce and diagnose. But let me give the reset a try by dumping the plist. Will let you know what I find.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points