That makes sense. I wonder if there is a better way to do it though, since It seems like this can be a little overkill with high frequency input devices like mice or analog joysticks. I'll have to check that out at some point.
On Tuesday, January 17, 2017 at 10:21:35 AM UTC+9, swiftcoder wrote: > > If you aren't re rendering the screen on a timer, it's really handy to > make your UI interactive :) > On Mon, Jan 16, 2017 at 4:19 PM Benjamin Moran <benmo...@gmail.com > <javascript:>> wrote: > >> I wonder what the original logic was behind flipping the window buffer >> every time input occurs... >> >> >> >> On Tuesday, January 17, 2017 at 12:30:11 AM UTC+9, Peter Schmidt wrote: >>> >>> @DXsmiley >>> Hmm, honestly, just the "window.invalid=False" seemed to do the trick, >>> without needing to do anything else. Using window.flip() made the frame >>> rate constant but at 30FPS. This is working smoothly now, so I'd say this >>> is solved. >>> >>> Thanks a lot! >>> >> -- >> 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...@googlegroups.com <javascript:>. >> To post to this group, send email to pyglet...@googlegroups.com >> <javascript:>. >> 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 pyglet-users+unsubscr...@googlegroups.com. To post to this group, send email to pyglet-users@googlegroups.com. Visit this group at https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.