Luca008
Comments
@Torabi
What do you mean by "there's mention of changing the keybinding for "Use Item"" ? "Button 2", aka ctrl+click, should act as a right click, so binded to "Use Item". What's the point in having a workaround in the first place if this wasn't the case? Most Mac users don't have a right click option.
I inserted it in that report's description to clear out doubts, although it wasn't necessary as it probably is already set by default.
I doubt the order of press has anything to do with this problem. The command ctrl+click gets correctly recognised, but incorrectly managed/released, if at all.
As for Mattias comment, I agree. I buy a product from Mojang, and if there are problems, it's up to Mojang to solve them, in a way or another. It's not up to me to solicit fixes to third parties. I don't care about what libraries the game uses - I care about the product that I buy. The company that produces the game is responsible for the libraries used.
The description of this report is incomplete. MC-26407 has a more complete description. It also applies not only to creative, but to the other game modes.
I highly doubt there is no workaround possible at a high level. It's easy to recognize flags using the Carbon framework in OS X, and I have never had issues with it.
Why does the temporary fix cause Minecraft to believe ctrl+click remains pressed after it has been released? Because this is the deal. Again, I think MC-26407 's description is way better than this one's.
I'm not aware of a bug in Apple's frameworks that incorrectly prolongs key presses. So the flaw must reside in the fix. It would perhaps be of interest knowing how the ctrl+click gets currently recognised.
Hey Mattias,
Unfortunately it is bound to happen to any OS X computer. I have tried it on both desktops (iMac) and laptops.
I agree that it's making the game unplayable. The only "fix" is to press esc every time you place a torch, which I can't tolerate anymore. Hopefully they're going to fix it as soon as possible.
@Torabi
This bug has nothing to do with Minecraft being unable to recognise ctrl+click as "Button 2", or as key code 99. This was reported in separate reports, and has already been fixed.
The bug we are discussing about deals with "Button 2" commands not getting released.
Ctrl+click translates correctly to "Button 2" (key code 99), but it won't get released. It gets triggered correctly as expected, but it remains active.
Checking options.txt is useless, as "Button 2", or right click, is always linked to that key code. For reference: http://www.minecraftwiki.net/wiki/Key_codes
Just to clear out doubts, you stated "possibility that assigning "Use Item" to anything other than "Button 2" will cause conflicts with that hack". The problem is that "Button 2" set as "Use Item" doesn't work as expected. So the "hack" used isn't producing the desired effect. There is no mention of conflicts with other key bindings.
Again, MC-26407 provides a better description.