I thought that there may be cases where you could use the ActionConfirmWidget to help stage a process to the next step. The process may not need confirmation but it allows you to break one step in two, with a conditional âcontinuationâ.
On your first post, I think it may be a little too general in some ways and I am not sure I understand;
You see one button is âone clickâ but within it you can have multiple steps
<$button>
<<step-1-actions>>
<<step-2-actions>>
<<step-3-actions>>
label
</$button>
- Within the actions macros or in the button widget you can wrap the actions macros in conditions including but not limited to the modified variable for held keys like ctrl
- ie one cation can be conditional on the result of a previous one.
But then buttons can also be in series with conditionals, so you could have say three buttons but only one of the three shows at a time, click action and display to the next button. If you gave them all the same name the user would be none the wiser than thinking it was the same button each time, however to motivate action the button is more likely to prompt clicking, through its button name.
- I have often had a replacement button appear only after the first has done its job successfully.
In your three step example âif any errorâ could display (again) the âcompute all errorsâ button, but if no errors just close the tiddler.
Personally I find building multi-step processes first manually, where the user/designer/I have to interact every step first, is a good way to build and test my code, but as I become more aware of the detail in the steps I see ways to âcollapse a number of steps into a smaller number of stepsâ, sometimes even eliminating any interaction altogether.