You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling the full App::update when the application is hidden (background thread or minimized on native, for instance) is bad for several reasons:
A) we don't always know what the size of the viewport is/should be
B) we pay the cost of GUI even though we may only need to process some events
I think therefor it makes sense to split App::update into two functions:
traitApp{/// You can run logic here, but can't show any GUI.////// Called once before each call to [`Self::show`], but may also be called/// without a subsequent call to `show`,/// for instance if the application is hidden and [`Context::request_repaint`] has been called.////// The egui context may ONLY be used to schedule repaints, nothing else.fntick(&mutself,ctx:&egui::Context,frame:&mutFrame){}/// Show the GUI. Each call to this is preceded by a call to [`Self::tick`].fnshow(&mutself,ctx:&egui::Context,frame:&mutFrame);}
Ideally we should do this without too much of a breaking change though
The text was updated successfully, but these errors were encountered:
Calling the full
App::update
when the application is hidden (background thread or minimized on native, for instance) is bad for several reasons:A) we don't always know what the size of the viewport is/should be
B) we pay the cost of GUI even though we may only need to process some events
I think therefor it makes sense to split
App::update
into two functions:Ideally we should do this without too much of a breaking change though
The text was updated successfully, but these errors were encountered: