Difference between revisions of "Shutter:Workflow"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
The workflow of [[Shutter]] is a simple 3-step process: | The workflow of [[Shutter]] is a simple 3-step process: | ||
| − | #Add [[Shutter:Events|events]] that are to be monitored, and | + | #Add [[Shutter:Events|events]] that are to be monitored, and |
| − | #Add [[Shutter:Actions|actions]] that are to be executed when the specified events occur. | + | #Add [[Shutter:Actions|actions]] that are to be executed when the specified events occur. |
#Start monitoring for the specified events. | #Start monitoring for the specified events. | ||
| − | The details are as follows: | + | The details are as follows: |
=== Step 1: Load Events === | === Step 1: Load Events === | ||
| Line 15: | Line 15: | ||
*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.<br> | ||
| − | Note that this action only loads the events; Shutter will not start monitoring for the event till you press the Start button. | + | Note that this action only loads the events; Shutter will not start monitoring for the event till you press the Start button. |
=== Step 2: Load Actions === | === Step 2: Load Actions === | ||
| Line 26: | Line 26: | ||
*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! | *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! | ||
| − | === Step 3: Start monitoring === | + | === Step 3: Start monitoring === |
| − | Press the Start button. Shutter starts monitoring for the events. | + | Press the Start button. Shutter starts monitoring for the events. The button changes to stop. Press it if you want to stop Shutter. |
| − | The button changes to stop. Press it if you want to stop Shutter. | + | |
| + | *Shutter also has a [[Image:ShutterNowButton]] button. You can start all actions without waiting for events. | ||
| − | |||
:This is useful to check how the specified actions would actually work. | :This is useful to check how the specified actions would actually work. | ||
Revision as of 10:51, 27 May 2010
The workflow of Shutter is a simple 3-step process:
- Add events that are to be monitored, and
- Add actions that are to be executed when the specified events occur.
- Start monitoring for the specified events.
The details are as follows:
Step 1: Load 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.
Note that this action only loads the events; Shutter will not start monitoring for the event till you press the Start button.
Step 2: Load 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!
Step 3: Start monitoring
Press the Start button. Shutter starts monitoring for the events. The button changes to stop. Press it if you want to stop Shutter.
- Shutter also has a File:ShutterNowButton button. You can start all actions without waiting for events.
- This is useful to check how the specified actions would actually work.