Below is a list of all available events.
Remember that Shutter is often used with a set of multiple events (rather than a single event); and these events have a pre-defined relationship between them.
||Count down a specified amount of time. This Event is considered "triggered" when the timer reaches zero.
- If you suffer from RSI, set timer to take a break every few minutes and exercise your hands, shoulder and neck.
- Use Shutter as a count-down timer clock (to give alarm at the end of specified time).
- Play a pre-recorded sound every few minutes (to calm down a baby or a pet).
||Event is triggered when the current time (as displayed in the system tray) reaches the specified time.
- Launch an application (e.g. a downloader) at certain time.
- Share your PC on LAN till a particular time, and then turn it off at certain time.
||Event periodically checks the playback state of Winamp. The event is triggered once it is detected that application is no longer playing the media.
Note: Winamp Messaging API is used to achieve this.
- When the WinAmp playlist is over, pause for a specified time period and then play another playlist, or hibernate the PC.
||Periodically check the processor usage and trigger event when the usage stays above (or below) the specified mark for the specified amount of time.
- Launch a CPU-intensive application (e.g. Blender rendering) to get the benefit of full CPU power.
- When CPU usage goes above certain threshold, pause the resource-intensive applications.
||Check the network's load (select from total, upload only, or download only); and if it falls below specified limit for the specified duration, then the event is triggered.
- Start a downloader when the download is below a limit.
- Upload a large folder when the upload falls below certain point
- Pause file-transfers till the total traffic in the network falls below a certain limit.
Track the time of user's last mouse and keyboard activity. Trigger the event when the user has been inactive for the specified period of time.
Methods for monitoring user inactivity:
- Last Input Event - Uses GetLastInputInfo API. Captures activity only of the initiating user session. The most stable and the least intrusive approach.
- Low Level Hook - Uses SetWindowsHookEx(WH_KEYBOARD_LL) and SetWindowsHookEx(WH_MOUSE_LL) API. Captures activity from all user sessions. Applied without injection into foreign processes to achieve a less intrusive effect, contrary to the official documentation, so it may stop working in future versions of Windows.
- Injection Hook - Uses SetWindowsHookEx(WH_KEYBOARD) and SetWindowsHookEx(WH_MOUSE) API. Captures activity from all user sessions. A tiny dedicated library file is injected into all foreign processes to capture user activity across all applications. This is a well established approach which may yield better results in some cases, but it is the most intrusive approach.
- Play WinAmp when no one is using the PC (turn the PC into entertainment center).
- Launch a task that can otherwise slow down the PC.
||Monitor power battery level and trigger event when level drops below specified level.
- Take backup of critical data.
- Close specified applications gracefully.
- Remind the user to plug in the laptop charger.
Monitor opened windows for the specified title match. Event is triggered when specified title does not match any of the opened windows.
- The name is NOT case-sensitive.
- You can specify wildcards to find a partial match. For example, *Firefox*.
If you do not use wildcards, Shutter will look for an exact match (if the actual Window name has more characters compared to the specified string, Shutter will treat it as "not matching").
Note: Be careful when specifying the window name: The text should match with what you see in the Title Bar of the application (the top bar of the application's window). Sometimes the Title Bar shows the file that is opened in the application, instead of the application's name.
- Warn the user that the desired application has stopped running.
- Launch the process only if the application is not running already (to avoid multiple instances running simultaneously)
||Monitor all processes that match the specified filename. Event is triggered when the specified filename is not found in the list of executing processes.
- Warn the user that the process has stopped.
- Launch the next process in sequence.
||Ping the specified host and trigger when host is not responding for the specified period of time. Useful for monitoring availability of network services.
- Warn the user that the remote PC is not communicating any more (either bad link or crash).
||Periodically check the size of the specified file and trigger the event when the selected condition is met.
The list of available conditions:
- file reaches a certain size;
- file is created;
- file no longer exists.
Internally, when the file or directory does not exist, it has an effective size of "-1".
- Take a backup of the file.
- Warn the user that the file size has reached the limit.