Iāve noticed (in my development environment and in published apps) the following scenario occurring:
I enter a Step which has a MapView, the MapView calculation begins. Before it finishes, I move on to the next Step. The āworkingā status remains visible in the upper right corner, and I cannot press buttons (this remains the case for at least a minute, Iāve never bothered waiting longer). Only when I move back to the previous Step and let the MapView be generated, I can continue on again.
The scenario is relevant in the context that someone has carried out most Steps, and just wants to scroll through them to check some things here and there - or when Iām developing something in distinct Steps and quickly want to move between them.
The same might occur for different Views, but I havenāt tested this.
Am I doing something wrong/is there a way for me to prevent this from happening, or is it possible for you to prevent this from happening?
Thank you for posting this. We will have to dive into this matter further, but I totally agree that this should not happen, as this will give a bad user experience to any user. Iāve added this to our internal issue tracker, and will relabel this as part of the āBug & Error Reportsā.
It might not be connected at all but I found a problem connected with Viktor PDFView (with duration_guess < 4). Assumptions:
Multi step application with few tabs of PDFView on first step
When user will try to click āNext stepā button (from 1 step) before all tab views are loaded completely, it will cause an error. It is crashing app even after the tab views will finish loading, so the user can not move forward until the whole app will be restarted.
Thanks for looking into this @mslootweg. I have managed to reproduce this issue just now, but I also see a way around this. For the Entity in which this problem occurs, the duration_guess for MapView was way too small compared to the time required to load all geometries. With the appropriate duration_guess, the MapView loading stops (the āupdateā prompt appears) and I can move onto another Step and click buttonsā¦
So now Iām wondering: are you able to reproduce this issue by creating a similar scenario?
The problem appears solved in the sense that proper duration_guess-configuration solves/prevents it, so Iām interested to hear what you think youāll (not) do with this caseā¦