Mousereleased mousebutton on default renderer

[processing-bot]

Created by: GanerCodes

When using mouseReleased, on the default renderer (not P3D for example) mouseButton is always zero. You can still see a button type (1, 2, 3) if you pass in MouseEvent and call getNative() on it.

[processing-bot]

Created by: oseph

Can confirm this behaviour on my end using macOS.

I'm looking at handleMouseEvent(MouseEvent event) method in PApplet and can't seem to make sense of why this might be happening. I'm new to contributing but I'd be happy to investigate further if someone can point me in the direction.

While I was there I also noticed code to allow macOS users to ctrl-click as right mouse, but this does not seem to work either.

[processing-bot]

Created by: behreajj

Hi @oseph , maybe in PSurfaceAWT, due to this update on Jan. 20. My hack to deal with this, based on @GanerCodes suggestion, is here. I was not able to test on Mac.

mouseClicked is impacted as well as mouseReleased.

[processing-bot]

Created by: oseph

Alrighty, I think I fixed this bug in #188. Feel free to try it out. Works on my end but I only tested on macOS. Give it a spin if you're using Linux/Windows!

[processing-bot]

Created by: behreajj

Hi @oseph,

Thanks for all your hard work. If I were you I would split this into 3 separate pull requests: one to fix the mouse released/clicked issue, one to fix the mac os control click issue and one to introduce new constants for mouse events. I'm only a random person on the Internet, mind you, trying to keep his own library working. This is just my 2c.

[processing-bot]

Created by: oseph

@behreajj thank you! That sounds totally reasonable to me. I'm still a little new to this whole contributing thing, so would be happy to do it the proper way. I'll close/cancel this pull request and split it into 3 separate ones.

[processing-bot]

Created by: benfry

Fixed for the release after 4.0 alpha 5 (either 4.0 alpha 6 or beta 1).

[processing-bot]

Created by: github-actions[bot]

This issue has been automatically locked. To avoid confusion with reports that have already been resolved, closed issues are automatically locked 30 days after the last comment. Please open a new issue for related bugs.