Hi Dan
Sorry, it was already late. Yes it worked. Your demo was giving the
right deltas and I was able to play the game (which was impossible before).
Thanks for your work too.
I didn't bother to look at the other QS_* constants. Maybe the
QS_RAWINPUT is newer and didn't exits when pyglet was written.
~DR0ID
On 13.11.2017 10:08, 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.
