Matan Addam

[As per the documentation](https://pyglet.readthedocs.io/en/latest/modules/window.html#pyglet.window.Window), for drawing a pyglet drawing batch in a multi-window application, this type of error is avoided by abiding by the guideline from the documentation: > To...

@mrzapp just wondering, what makes this better than drawing multiple pyglet lines other than maybe speed?

I would probably add that to the documentation, or a general note about multi-threading when using pyglet, as it may come up in many applications whereby the cost of redesigning...

Regardless the location (anything that will show up in search beyond this Github issue in itself, should be helpful). It's actually helpful as well, to delineate what _can_ be done...

Currently `Window.set_size` has this line of code in it: ```python self.dispatch_event('on_resize', width, height) ``` Which means that when called by application code, it may directly steer the flow of control...

I see that the google groups is very low traffic, so just linking here to a use case where animation support could avoid awkward ways of accomplishing the same. https://groups.google.com/g/pyglet-users/c/hxXXtkwcH0I/m/WidEiQKMBgAJ....

Well if it helps anyone more than being a distraction, I wrote some code to bypass the stack nature of the current callbacks registration implementation. I hope this is concurrency...

Okay I get it, I guess that the event loop will never go on to the next callable queued on it before finishing the current one. I guess this would...

A callback will in some cases start executing from within a callback triggering it, rather than being queued for execution for after the current callback has returned. I would call...

In one interesting case, though only circumstantial, this also breaks the event loop itself when pushing the confluence one step further. In this stack trace, the execution of a keyboard...