Problem: Currently we have to use two or even more scripts if we want to use cards or layouts as dialogues. First we have a script that opens the card/layout as a dialogue and perhaps prefills fields by parameters. Then we need at least one further script for handling the buttons with parameters for OK, abort or what actions can ever be taken. Probably many users will create one script for every button. So you get a bunch of scripts for even simple tasks, instead of one readable script.
Solution: All this could be eliminated, if we had two new script steps:
- "Wait for user" would pause the script, but not like the current "Pause"-script step. It would only allow the user to fill the fields of the current layout AND click one of the given buttons. All other functionality would be unavailable. So the user would at least have to intentionally abort the dialogue layout/card. The user shouldn´t be able to quit the app without taking a decision.
- "Continue" would grab the parameters of the buttons and stop "Wait for user". "Continue" on button 1 with a parameter 1 for example would than call our paused script again and go on after "Wait for user". Here we could have an if-then-else construct and handle for example parameter 1 as "abort" and parameter 2 as "OK".