When running a long-running script, I notice that Opus automatically shows a 'long-running task' indicator (e.g. in the jobs bar, if configured to do so).
However, during this particular script I'm working on (the checksum checker), I know how long I'm going to take. e.g. I know how many files will have checksums calculated for them.
Is it possible to provide these counts as information to the progress indicator so it can show the user something sensible?
Perhaps something like Script.UpdateProgress(min, max) or even just Script.UpdateProgress(text).
I think one progress dialog is for the button (@nodeselect and the other two lines) while the other progress dialog is for the script.
If you do everything from a single script-button, it should work how you want.
You may also be able to avoid the button's progress dialog by removing {allfilepath$} and having the script command pick them up implicitly, as I suspect that's what's triggering the unwanted progress dialog.