Information Project Miscellaneous

User Manual - OutputHandlers

OutputHandlers control, which actions are execute, when, how many times and if any action is executed at all. This page gives you an overview over all available OutputHandlers.
As most definitions are executed by a pressing a button on your remote, "executing a definition" mostly equals "pressing a button" on this page.


AB-Handler know two states: A and B. The determination, if the current state is A or B, is made in different ways (see below). All AB-Handlers allow you to specify a group of actions to each of the states:

  • In turns: A executes actions no. 1,3,5,7,... from the action list (every second one), B executes no. 2,4,6,8,... (the other ones).
  • First or rest: A executes only the first action, B the rest.
  • All or none: A executes all actions, B doesn't execute anything at all.

Execute in turns

This handler changes its state every time you execute it. So the first time you execute the definition, its state is A, the second time, it is B, the third time, it's A again. This behaviour is useful to switch things off (e.g. the screen) and turn them on again - with a single button.

Window active? and Window open?

These handlers allow you to choose a window. If this window is open respectively the active window, the state is A, if not, it's B. You could for example change the master volume with the volume keys on your remote - except for when Windows Media Player is open, because you would want to change the WMP volume then.

Process running?

This handlers's state is A, when a specified process is running, otherwise it's B. This enables you to start an application, if it's not running yet and close it, if it is already running.

Short/Long key press

To use this handler, you should use an event with the key states "Press" and "Release" in your definition. The handler measures the time that passes between the first and the second execution (i.e. between pressing and releasing the button). If the time span is smaller than the specified interval (750 milliseconds is an intuitive value), the state is A, if the time span is bigger, the state is B. You can for example setup a button to suspend your computer on a short-time press and to shut it down on a long press.

Other OutputHandlers

Adjustable timer

When you execute this handler, you will be asked to specify a time span (using the OSD), that will be waited before executing the actions. You can for example configure a button to display this timer and then enter e.g. 15 minutes (with your remote) to have your computer shut down after 15 minutes. Executing the handler again while it is waiting will stop the execution.

Deferred execution

This handler executes all actions after a specified time span - and therefore delays the execution.

Defer single actions

This handler allows you to set up an interval for each action. If you for example specified 10;50;;60 for the intervals, the first action would be executed after 10 milliseconds, both the second and the third one after 60 milliseconds (after your keypress) and the fourth as well as all remaining actions after a total of 120 milliseconds.

Repeat after specified interval

This handler executes all actions once and then repeats the execution after a specified interval.

Multi execution

This handler executes all actions x times in a row.

Execute only nth action at nth execution

This handler executes the first action on the first keypress, the second one when you pressed the button the second time, etc. If you have e.g. 6 actions, the first action will be executed when you press the button the seventh time.


This handler uses the OSMenu to let you choose the action to be executed. Read more about using the OSMenu here.

Confirmation prompt

This handler shows a message with a specified text, when it is executed. If you confirm the message (Yes), all actions are executed, if you don't, nothing happens. The message can also be confirmed by pressing the OK button on your remote and can be cancelled with the Back or Delete button.