On 13/06/14 11:12, Griatch Art wrote: > You are of course correct that vastly more time is spent in the > handlers rather than in the event loop. It still doesn't change the fact > that the event is sort of "out of the hands" of the regular developer > and should operate as quickly as possible (it's in C in some > frameworks). In this case I would just think that "optimizing" the event > loop is a simple enough thing that it might be worth considering. :)
Just open a bug report with all the info and a patch. https://code.google.com/p/pyglet/issues/entry It may not make a big difference, but if something is obviously unoptimized and there's not a good reason for it, we should improve it if we can. Regards, Juan -- 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 http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
