Difference between revisions of "Shutter:Workflow"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
[[Shutter:Events|Events]] are usually based on periodic checking of a system state, execution state of a process, or system time. | [[Shutter:Events|Events]] are usually based on periodic checking of a system state, execution state of a process, or system time. | ||
| − | *You can add multiple events, and also set the logical relationship between them. <br> | + | *You can add multiple events, and also set the logical relationship between them. |
| + | *Check the order of the Actions: Any action must not affect the other actions listed below it.<br>Also ensure that the terminal action (if any) is listed at the end.<br> | ||
=== Step 2: Actions === | === Step 2: Actions === | ||
Revision as of 05:16, 27 May 2010
The workflow of Shutter is quite simple:
- Add events that are to be monitored, and
- Add actions that are to be executed when the specified events occur.
The details are as follows:
Step 1: Events
Events are usually based on periodic checking of a system state, execution state of a process, or system time.
- You can add multiple events, and also set the logical relationship between them.
- Check the order of the Actions: Any action must not affect the other actions listed below it.
Also ensure that the terminal action (if any) is listed at the end.
Step 2: Actions
Actions are executed one by one, from top to bottom.
You can add as many actions as you want, but please be aware of the following factors:
- Each action can affect the execution of the other actions listed below it.
- Some of these actions are terminal.
(They will cause Shutter to stop processing the rest of actions or terminate application altogether. For example: the Shutdown action.)
Therefore, such Actions must be placed at the very end of the Actions stack.