Daniel, Good suggestions. As for prompting, I too find myself in situations (mostly because I'm always installing new versions of QRecall for testing) where I don't want a bunch of scheduled actions to start running. Being able to stop them would be handy. On my to do list is a feature request to put up a prompt/dialog before an action starts (this would be an option in the action's schedule), allowing you to start it immediately or cancel. If you don't respond to the dialog in 60 seconds, it would proceed automatically. As for a "once action X has finished" event, how do you see this as materially different than scheduling the subsequent actions to run after the first? My original concept for a sequence of actions is that they would simply be scheduled to run in order (capture at 1:00, merge at 1:01, compact at 1:02). The scheduler automatically takes care of not running them concurrently.
|