i have a 21.5 inch iMac and after using the expose feature for about 30mins or so it acts strange. i normally use it through the 3rd 'squeeze' buttons on my mighty mouse but it happens with the expose button on the keyboard too. when i activate expose it chucks all the windows out but then brings them all back straight away where before it used to chuck em out n scatter them until i pressed it again. i tried changing the mouse and keyboard and did a software update too but no luck. the same thing happend in my previous 20inch aluminium iMac, any ideas?!
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
has anybody had any problems with expose?
- Thread starter ruk110
- Start date
- Sort by reaction score
Do you have any windows minimized to the Dock? I had this very same problem, but it only happened whenever I had more than 6 windows minimized.
I solved it by reverting to an earlier Dock.app, which was from a developer preview of Snow Leopard (before they changed how Expose works). Incidentally, I prefer the way that older versions of Expose arranged the windows, so it was win-win for me
.
I solved it by reverting to an earlier Dock.app, which was from a developer preview of Snow Leopard (before they changed how Expose works). Incidentally, I prefer the way that older versions of Expose arranged the windows, so it was win-win for me
.YES. I have this problem. I just bought a refurbished 27" iMac, and this has happened to me constantly in the last day. Basically, if you've got more than 4 windows minimized in the dock and hit expose on all windows, it activates but then snaps back right away. You have to actually hold down the button in order to get it to stay "exposed". But if you "maximize" those minimized windows, it goes back to normal. Even then, performance changes depending on how many windows are minimized. If you've got none minimized, it's smooth. No lag. If you've got like 3 or 4, expose doesn't animate smoothly -- it just jerks right away into expose mode.
I installed all software updates and it's still like this. I'm going to call Apple Support tonight.
Edit: I read through some of the post that dolphin842 linked to but, honestly, this shouldn't be something I have to work around in order to fix it. It should be working smoothly by default. If not, then there's a problem. So I'm going to call Apple support and see what they say.
I installed all software updates and it's still like this. I'm going to call Apple Support tonight.
Edit: I read through some of the post that dolphin842 linked to but, honestly, this shouldn't be something I have to work around in order to fix it. It should be working smoothly by default. If not, then there's a problem. So I'm going to call Apple support and see what they say.
The buttons (both on the Might Mouse and the keyboard) have two distinct behaviors. If you click/press quickly, Expose is invoked and stays that way until you click again. If you click and hold, Expose is invoked and only stays until you let go of the button.
So, if you are holding the button down too long, you will see the behavior that you described.
A.
While it's true that Expose will normally snap back if you hold down the button for a while and then release it, the problem that the OP describes is indeed a bug in how the new Expose works, and is easily repeatable for those it affects. The snapback occurs no matter how quickly you click or press the button.
I'm pretty sure this is just how the new Expose works. Certainly for me, it's a big step back. I didn't use the new Expose for months because it was so frustrating. Once I went back to the old version I found I was using it instinctively again. It's going to be a sad day whenever 10.7 or a point update comes out and prevents me from using the old Dock.app. If enough people are annoyed by this, it might be worth trying to get some sort of organized statement so Apple at least is aware of the demand for a better-performing Dock in the next OS X revision.
If you do get in touch with Apple, please share any response they have.