Jerome Humbert

Thanks @nicopap for the detailed answer. I was skeptical about whether the change goes in the direction of uniform component/asset handling because of the various new `Asset`-prefixed types, which make...

@cart > I believe we could store change ticks on Handles, if we're willing to store ticks as something like `Arc`. I see that `Handle` is an `Arc` to a...

I just hit the same bug (on 0.13), and I don't have any nesting, just a `Handle` inside a custom `Resource`. I need to upgrade to 0.14 see if that...

> Anyway, I get how this new stateless system is more flexible and such, but I think the upgrade documentation was way to minimal to be of use to people...

I found https://github.com/bevyengine/bevy/issues/7258 back from January to add to the list of missing things. I'm a bit surprised this was cut from release given it clearly highlights that users _will_...

I see how that can be useful, however I have a few questions (not necessarily to you): - The default setup in Bevy will use `Time` in `Update`. It's unclear...

I should add that my experience with Unity has been that time scaling is seldomly used, as it's too broad. If you want to implement a "pause system" (generic term...

I mean, to be clear it seems a very good addition to be supporting the various `Time` for tweening. I have no objection on that, I'm convinced this is the...

That sounds reasonable I think.

Yes we could add that. Although really `Tweenable::tick()` is not really designed to be used manually by default; instead the `component_animator_system()` will call it automatically. You can have a look...