I was walking around punching some trees in amplified mode successfully after updating to 1.7.2, when I thought I would have a look at my framerate to see how taxing amplified terrain is.
So I tried to hit Ctrl-F3, but I had forgotten that my keyboard wasn't set to use F keys by default (I was supposed to also hold down Fn.) So by accident, I had actually activated "Application windows" in Mission Control (also bound to F10 by default.)
On returning to Minecraft, I couldn't stop punching the tree.
I hit Esc to get to the menu to try and reconnect and found that it wasn't possible to use the mouse there either - I was stuck in the game.
On going back into the game, I wasn't punching the tree any more, but I couldn't punch anything any further. Game over. :>
I thought it was nuts, so I tried it again from the top and it turns out to be completely reproducible on my computer. That said, this is my work computer, so I will try again some time on my home one.
Linked issues
Comments 3
Confirm on 13w33c through 1.8-pre1 Single Player, Mac OS X v10.9.4.
I had the 4th button on my mouse set to activate Mission Control, and when I accidentally clicked it, the game doesn't pause. If I click the left/right mouse button and the Mission Control button at the same time, the left/right mouse button is stuck, and I have to pause/unpause the game to fix it.
I think having the game to pause when Mission Control is activated would fix the problem.
Why is this marked as duplicate? MC-1519 is about toggling fullscreen and this is about Mission Control in Mac OS, they are totally different.
Also I should add that I know it's only F3 to bring up that screen, but for other reasons of Mac OS intercepting F3, I found I had to hold control. It looks like that is no longer the case though, after changing my work keyboard preferences to act as F keys by default, F3 by itself now brings up the stats.
In other words, now F10 triggers the problem instead. orz