Hi Torabi, thank you for your kind and patient response.
We have indeed read and comprehended Grum's comment. Thank you for adding it to the thread.
Reasons that people continue to respond:
Grum's original suggestion of just using a mouse suggests that he isn't a mac/laptop user. We are providing perspective.
Bugs in vendor libraries can indeed be addressed by a company. Mojang has worked with lwjgl to get issues addressed in the past. Please look on the net and you will see this. At the least a reference to the corresponding lwjgl bug would be helpful, but perhaps this is not available.
A closed bug with a quiet comment thread doesn't seem likely to get addressed. "May create a workaround" is better than nothing, but.
Most importantly, when I do a two-finger tap, I flub and end up hitting testificates in the head and my iron golem kicks my ass 🙂.
For the time being, I have remapped the right-click to "R", but the setting does not equally apply to inventory management (I still need a double-click to divide a pile in two, drop one element of a pile, etc.) It is confusing to have the remapped controls apply to placing the block but not to inventory management.
Since we can't vote for this issue (I think), I suggest that people who care add themselves as watchers for this issue.
I agree with above commentors. The bug is indeed ruinous for those on macbooks with no mouse. I would like to be able to vote for this issue. I'm frustrated to see it marked as invalid. Please help.
Is there any sort of bug report that I can track in LWJGL?
Here is the output from the development console.
Client> [14:37:33] [Client thread/INFO]: Created: 512x256 textures/blocks-atlas
Client> [14:37:33] [Client thread/INFO]: Created: 256x256 textures/items-atlas
Client> [14:37:35] [Netty Client IO #1/ERROR]: Channel became inactive!
Client> [14:37:35] [Server Pinger #3/ERROR]: java.lang.NullPointerException
Client> [14:37:37] [Client thread/INFO]: Connecting to <REMOVED FOR PRIVACY>, 25565
Client> [14:37:37] [Netty Client IO #3/ERROR]: Channel became inactive!
Client> [14:37:37] [Netty Client IO #0/ERROR]: Channel became inactive!
Client> [14:37:57] [Netty Client IO #5/ERROR]: Channel became inactive!
By the way, I would rename this bug as something more descriptive. I have seen a failure messages of NullPointerException as well as something like "Failed to connect to the server / Internal Exception: io.netty.handler.timeout.ReadTimeoutException"