That is what I'm doing now, but was looking to see how much I could push pyglet. ;)
Take care. On Dec 4, 7:31 am, "Alex Holkner" <[EMAIL PROTECTED]> wrote: > On Dec 4, 2007 11:27 PM, sol <[EMAIL PROTECTED]> wrote: > > > > > > > I should have also mentioned that we are overriding the time_function > > in Clock to use our high resolution timer. > > > On Dec 4, 7:23 am, sol <[EMAIL PROTECTED]> wrote: > > > I think a little background would be good. > > > > We write software for vision scientists where accurate reporting of > > > stimulus changes (visual, auditory, or otherwise) is critical. Very > > > often the programs will make changes to the display and then wait for > > > an event to happen before doing something else, like changing the > > > display again or play a sound or send a TTL signal to another device > > > etc. This means that there are periods where the refresh rate of the > > > display can gate the frequency of polling (like calling tick() or > > > calling dispatch_events), but much of the time polling can be done > > > many times a millisecond. > > > > This is the type of situation where having a mechanism for accurately > > > scheduling a callback for a future time is very useful. > > > > I believe the issue with the current implementation of schedule is > > > that if you call schedule_* during a period of low tick() call > > > frequency then this effects the ability of the scheduler to accurately > > > schedule the callback for a specific time even when the time in the > > > future has a very high tick() call frequency. Again, this is all fixed > > > in the current implementation if I call tick() right before calling > > > schedule, so no biggy here. > > Ah, this is making more sense now. Even with the high resolution > timer plugged into pyglet.clock, you can probably do a lot better by > managing the poll/sleep loop yourself, given your specific needs. > > Cheers > Alex. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
