Hi,
I'm using GLFW in my graphic program and I have also drag&drop implemented on my side. Everything works fine until system cancels drag&drop operation. When that happen, GLFW window doesn't detect that mouse button was released and it remains virtually pressed until next click.
That trouble is in Windows, in some cases it doesn't send message WM_LBUTTONUP.
Second solution could be some GLFW function I may call and GLFW window evaluates keys and mouse buttons states (seems little bit as a hack to me but I can survive this).
If you know any other solution, please let me know.
=asm=
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I'm using GLFW in my graphic program and I have also drag&drop implemented on my side. Everything works fine until system cancels drag&drop operation. When that happen, GLFW window doesn't detect that mouse button was released and it remains virtually pressed until next click.
That trouble is in Windows, in some cases it doesn't send message WM_LBUTTONUP.
First solution I've found is described there: http://www.drdobbs.com/avoiding-trouble-with-mouse-capture/184416474
In short: just handle messages WM_CAPTURECHANGED and WM_CANCELMODE and check real state of mouse buttons there.
Second solution could be some GLFW function I may call and GLFW window evaluates keys and mouse buttons states (seems little bit as a hack to me but I can survive this).
If you know any other solution, please let me know.
=asm=
Thank you! Please submit this to our issue tracker on GitHub so it doesn't get lost here.