test putting process in fixed update

[tomara-x]

and then dropping to a low duration

update is still reactive so when there's redraw events it should update, so when process is doing things that need a redraw it should work, right? (moving something, updating a display, etc)

[tomara-x]

you can still control fixed-update's rate

[tomara-x]

probe has an ambiguity. i think it's because sometimes process is run after, so whatever it updates (num in this case) sends a redraw event and so update is called again. but if it ran after, then it.. it doesn't make any sense, we need fixed update

[tomara-x]

oh fugg! the main schedule runs fixed update. so umm.. yeah lol

here's the tea: winit::UpdateMode controls how frequently App.update() is called update(): Advances the execution of the Schedule by one cycle Main: The schedule that contains the app logic that is evaluated each tick of App::update() FixedUpdate is in main :scream: :heart: :socks: :pregnant_man: :high_heel: :leafy_green:

[tomara-x]

this is not gonna work like that 6b3004d we need a different way