Charlie,
Yes thanks for that, I have taken this into account. In the application I am working on some startup actions to check for some conditions and if true, make changes, save the wiki and reload. The user never gets to interact until the wiki reloads in a particular state. So in this case this is not an issue.
If I am forced to use a timer (to give the save time to complete), because the other possibilities are not available, I will consider “Run once after some interval” from OokTech/TW5-TimerActions or perhaps Eric has something in TimerTools
Your points however do go to the subject of;
if a solution must be developed, could we try and make it generic in nature that it has a broader application?
I understand the idea of using the modal to take over the UI, which is a useful method. However it is worth noting this may not be necessary if;
- Actions bundled together under one trigger may run quickly. if they can run in parallel then they can step on each others toes. A way to force the serial execution of actions as a rule (if needed) would be another solution.
- There may be an argument for actions that can be initiated in the background eg save wiki to return interactivity to the user so they continue. In which case there may be another trigger that initiates an action that depends on the prior action completing and we want this second actions to be able to check or wait for the condition to be true.
- If we could time events we may be able to adjust a timer based on previous save times.
Just thought I would add here that perhaps we can use progress pie charts