Difference between revisions of "Shutter:Workflow"

From den4b Wiki
Jump to navigation Jump to search
(Created page with '{{Up|Shutter}} The workflow of Shutter is quit simple: monitor events and execute actions when events have been triggered. === Step 1…')
 
(Clarified the link between events and actions, and multiple independent schedules.)
 
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
{{Up|Shutter}}
+
{{Up|Shutter}}  
  
−
The workflow of [[Shutter]] is quit simple: monitor [[Shutter:Events|events]] and execute [[Shutter:Actions|actions]] when events have been triggered.
+
The workflow of [[Shutter]] is a simple 3-step process:  
  
−
=== Step 1: Events ===
+
#Add [[Shutter:Events|events]] that are to be monitored, and
 +
#Add [[Shutter:Actions|actions]] that are to be executed when the specified events occur.
 +
#Start monitoring for the specified events.
  
−
[[Shutter:Events|Events]] are usually based on periodic checking of some sort of a system state, whether it is current time or execution of a process. The scenario in which they will trigger actions is define by the selected [[Shutter:Logic|Logic]]. You can add as many events as you want.
+
Shutter monitors for the events to be triggered according to the [[Shutter:Logic|selected logic]], then all actions will be executed one by one. Note that individual events are not directly linked to individual actions, but the lists of events and actions are linked.
  
−
=== Step 2: Actions ===
+
You can consider that a single instance of Shutter has a single active schedule (preset). If you need multiple active schedules, you need to start multiple instances of Shutter each with its own schedule.
  
−
[[Shutter:Actions|Actions]] are executed one-by-one from top-to-bottom. You can add as many actions as you want but beware that some actions are ''terminal'', meaning that they will cause Shutter to stop processing the rest of actions or terminate application altogether, for example: Shutdown action.
+
=== Step 1: Add Events  ===
 +
 
 +
[[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 [[Shutter:Logic|logical relationship]] between them.
 +
 
 +
Note that this step only loads the events; Shutter will not start monitoring for the event till you press the [[Image:ShutterStartButton.png]] button (see '''Step 3''').
 +
 
 +
=== Step 2: Add Actions  ===
 +
 
 +
[[Shutter: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. <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'': 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  ===
 +
 
 +
Press the [[Image:ShutterStartButton.png]] button. Shutter starts monitoring for the events. The button changes to [[Image:ShutterStopButton.png]]. Press it if you want to stop Shutter in an emergency.
 +
 
 +
*Shutter also has a [[Image:ShutterNowButton.png]] button, which starts all actions without waiting for triggering the event-set.
 +
 
 +
:This is useful to check how the specified actions would actually work.
 +
 
 +
[[Category:Shutter]]

Latest revision as of 15:05, 15 April 2022

Arrow Return.png Shutter  

The workflow of Shutter is a simple 3-step process:

  1. Add events that are to be monitored, and
  2. Add actions that are to be executed when the specified events occur.
  3. Start monitoring for the specified events.

Shutter monitors for the events to be triggered according to the selected logic, then all actions will be executed one by one. Note that individual events are not directly linked to individual actions, but the lists of events and actions are linked.

You can consider that a single instance of Shutter has a single active schedule (preset). If you need multiple active schedules, you need to start multiple instances of Shutter each with its own schedule.

Step 1: Add Events

Events are usually based on periodic checking of a system state, execution state of a process, or system time.

Note that this step only loads the events; Shutter will not start monitoring for the event till you press the ShutterStartButton.png button (see Step 3).

Step 2: Add 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 ShutterStartButton.png button. Shutter starts monitoring for the events. The button changes to ShutterStopButton.png. Press it if you want to stop Shutter in an emergency.

  • Shutter also has a ShutterNowButton.png button, which starts all actions without waiting for triggering the event-set.
This is useful to check how the specified actions would actually work.
Retrieved from "http://www.den4b.com/w/index.php?title=Shutter:Workflow&oldid=3482"