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
Please see what happens when pop_until_active is used between 0:05 and 0:06:
Video starts on "installed" Dashboard screen, then 3 screens are pushed, then self.app.get_screen("dashboard").pop_until_active() gets called by binding from def action_dashboard
Screencast.from.10-03-2024.02.22.10.PM.webm
The text was updated successfully, but these errors were encountered:
I try to include MRE every time. Unfortunately, this time I tried to trigger it having several screens on the stack containing a placeholder widget and I couldn't reproduce it. Maybe it depends on the widgets on the screen, or updating them from a worker. That's why I included a video showing the behavior I'm talking about in a more complex app.
Generally, it seems to me that this might be some kind of regression because this problem was fixed some time ago and came back with new versions (we observed it before pop_until_active, when calling pop_screen in a loop).
I thought that the video itself could help and outline the problem a bit.
When I'll have some more time, will try to provide an MRE.
Please see what happens when pop_until_active is used between
0:05
and0:06
:Video starts on "installed" Dashboard screen, then 3 screens are pushed, then
self.app.get_screen("dashboard").pop_until_active()
gets called by binding fromdef action_dashboard
Screencast.from.10-03-2024.02.22.10.PM.webm
The text was updated successfully, but these errors were encountered: