Hi, I just checked a bit more, and it seems to happen because pyglet sets up user32.GetCursorPos to accept the correct types. According to msdn the argument is of type LPPOINT. In practice this is a pointer to a memory address, that is why it also accepts a raw int pointing to a memory address, but that is not the correct way to do that. You should really define a pointer to that memory address and pass that to GetCursorPos.
Rob Op zaterdag 23 mei 2015 04:29:36 UTC+2 schreef lhc...@gmail.com: > > > On Saturday, May 23, 2015 at 1:22:45 AM UTC+8, Rob wrote: >> >> Could you create an issue for this at >> https://bitbucket.org/pyglet/pyglet/issues ? >> >> Rob >> > > done. i wish pyglet group will soon fix this. > -- 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 pyglet-users+unsubscr...@googlegroups.com. To post to this group, send email to pyglet-users@googlegroups.com. Visit this group at http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
