Paul
Paul
Right, I need to figure out the zipballs since it's dependent on https://github.com/pyglet/pyglet/pull/1154
Zipball's fixed, but the other pyright issues belong in #2183.
I've dropped the zipball commits during rebase onto `development`. We're on `pyglet==2.1dev4` now.
@einarf @Cleptomania Given the pyglet 3.0 work, should I close this or leave it here as a reminder to look into the vectors?
@DigiDuncan Let me know if the relative position helper seems to belong in `Rect` or if I somehow missed one like it already existing.
> I would close this PR TL;DR: Agreed. This thing was an exploratory kludge. I want to review your recent UI event proposals for controllers before attempting this + thoroughly...
Could you please run `python -m arcade` and paste the output here? This command will give you a few lines of information, including your Arcade and pyglet version numbers. We...
To my understanding, are two ways to go about this: 1. Pillow + create a texture 2. Render directly into a texture as in the `PerfGraph` https://github.com/pythonarcade/arcade/blob/8be369966ada1ecdc0153168abac068ecb534f02/arcade/perf_graph.py#L15
It looks like thumbnail generation also doesn't fire when those files are updated.
> It this still a problem? **TL;DR:** Our pre-3.0 temp fix should work until we test and deploy upstream's fix for their 10+ year bug ## The Quick Fix >...