Hi Benjamin
AFAIK the mouse behavior was always this way, but the thing is that the
difference only started to show up with that win10 build. I can only
assume that in earlier windows versions the mouse behavior was not so
obvious and for some reason the coordinates where almost always as expected.
For the alt+tab problem: I would let the programmer of the application
deal with it instead of implementing logic in pyglet itself that handles
this. Of course this should then be documented or mentioned in a
tutorial how to deal with loosing focus (of the window) in mouse or
keyboard exclusive mode.
~DR0ID
On 17.01.2018 07:09, Benjamin Moran wrote:
Just as a follow up, It seems like this issue was caused by a recent
Windows 10 update, and it affected quite a few projects.
I'm not sure if it was a bug, or if Microsoft just "fixed" something
that had long behaved incorrectly.
We also have a new issue on the tracker about exclusive mouse mode.
The fix worked, but they had a few other comments about strange
behavior. Do you think this might be related to the change, or may
have already existed?
https://bitbucket.org/pyglet/pyglet/issues/158/windows-10-exclusive-mouse-bug
On Tuesday, November 14, 2017 at 11:17:03 AM UTC+9, Benjamin Moran wrote:
Dan,
This is really great. Thanks for updating the code, and also for
taking the time to write the unit test.
I'll give this a test on my Windows 7 machine as well, and please
go ahead with a pull request if/when you're ready.
DR0ID, thanks for the testing and feedback.
-Ben
On Monday, November 13, 2017 at 6:08:33 PM UTC+9, Daniel Gillet
wrote:
Hi DR0ID,
Thanks a lot for all the tests and the time spent figuring out
the problem.
I'm reading again the MSDN documentation and I was a bit
surprise. In the current code, we are waiting for QS_ALLINPUT.
According to the docs
<https://msdn.microsoft.com/en-us/library/windows/desktop/ms684242%28v=vs.85%29.aspx>,
it's defined as: This value is a combination of *QS_INPUT*,
*QS_POSTMESSAGE*, *QS_TIMER*, *QS_PAINT*, *QS_HOTKEY*, and
*QS_SENDMESSAGE*.
Looking atQS_ALLINPUT, it's defined as: This value is a
combination of *QS_MOUSE*, *QS_KEY*, and *QS_RAWINPUT*.
So here we do have the raw_input. So I've been looking at
pyglet/libs/win32/constants.py and here is what I found:
QS_INPUT = (QS_MOUSE | \
QS_KEY)
So the raw_input is missing!!!
I will make a new commit with that bug fix.
You did not really specify in your message if in the end it
worked for you or not.
Dan
--
You received this message because you are subscribed to the Google
Groups "pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.
