This problem is on macos. On linux mint when the scroll button is pushed, button 3 is returned (not button 2 as on macos).
The left button (button 1) and the right button (button 2) work fine.
If you activate the scroll button by scrolling and pressing, the software says you activated button 2 (this is a poor choice, since button 2 is the right button). A second activation of onclick allows access to
mfb-get_mouse_scroll_x and
mfb-get_mouse_scroll_y
This is ok, but now all future calls to mfb-get_mouse_scroll_x or y. (with no scrolling of the mouse) will return the same value as was returned initially. For me, when the scroll button is pressed, code to return button 3 with access to the screen x,y values would be great.
This problem is on macos. On linux mint when the scroll button is pushed, button 3 is returned (not button 2 as on macos).
The left button (button 1) and the right button (button 2) work fine.
If you activate the scroll button by scrolling and pressing, the software says you activated button 2 (this is a poor choice, since button 2 is the right button). A second activation of onclick allows access to
mfb-get_mouse_scroll_x and
mfb-get_mouse_scroll_y
This is ok, but now all future calls to mfb-get_mouse_scroll_x or y. (with no scrolling of the mouse) will return the same value as was returned initially. For me, when the scroll button is pressed, code to return button 3 with access to the screen x,y values would be great.