Korijn van Golen
Korijn van Golen
> * Emit a custom "update event" that animations can use. (we currently call this "before_render"). I assume this would be emitted by the GUI layer, right? Not by anything...
> The main question is how to let animations (e.g. controller smoothing) do updates. The above is one solution. I really like your proposal because it means the renderer and...
We have seen the following examples in our current codebase that would need an update event: * Controllers * Gizmo * Helpers (light helpers are an example, but the other...
I think what we should do here is (in order): 1. Define the update modes we want to support 2. Define the API requirements and design for the GUI layer...
# Update modes * Unlimited/continuous * [ ] Verify that indeed it is possible to render at unlimited FPS and it is not still limited by some factor (e.g. vsync,...
Brainfart: The vision is that the renderer should be just that: a renderer. Events and wobject lifecycles should be implemented outside of the renderer. I'm thinking of implementing some kind...
I'm not sure. It seems like an independent problem to be honest.
> What do you mean with "wobject lifecycles"? Do you mean the wgpu objects for a wobject (i.e. `pipeline.py`)? It's complicated. I feel that the thought has not fully come...
Great overview!
I think the important thing for me is that pygfx is a rendering library, not a gui framework. It feels like we are very prone to feature creep, leading to...