Difference between revisions of "Shutter:Workflow"
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
You can add as many actions as you want, but please be aware of the following factors: | 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. <br>To avoid that, you may have to change the order of the Actions by moving them up/down. | + | *Each action can affect the execution of the other actions listed below it. <br>To avoid that, you may have to change the order of the Actions by moving them up/down. |
| − | *Some of these actions are ''terminal'' | + | *Some of these actions are ''terminal'': They close Shutter, log out the Windows user or shut down the PC. (For example: the '''Shutdown''' action.)<br>Therefore, such Actions <u>must</u> be placed at the very <u>end</u> of the '''Actions''' stack. Otherwise the actions listed below them will ''never'' be executed! |
Revision as of 05:20, 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.
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.
To avoid that, you may have to change the order of the Actions by moving them up/down. - Some of these actions are terminal: They close Shutter, log out the Windows user or shut down the PC. (For example: the Shutdown action.)
Therefore, such Actions must be placed at the very end of the Actions stack. Otherwise the actions listed below them will never be executed!