Actions

After selecting a remote or a mode, you can add actions to it using the + button on the right. There are two different ways how actions can be created. By using a template or by browsing the D-Bus session bus manually.


Adding an action

Creating actions using templates is easier but limited. You can find templates for the most common applications such as Amarok or the KDE program launcher and system commands for shutting down your computer. Those templates are collected in profiles that group them into similar task. For example there is a Profile called Power management that contains templates for shutting down or suspending your computer.


Adding an action using a template

Creating actions by browsing the D-Bus lists all currently running applications. You can browse through them and their functions. This requires a basic understanding of how D-Bus works, but you can use more applications and functions than those in the template list.


Adding an action using D-Bus

When adding an action you can tweak a few more options. The first one of them defines if the actions is executed repeatedly when the button on the remote control is being held down. This is a useful behavior for actions like increasing or decreasing volume but may be undesired for actions like toggling play/pause on a media player. The second one defines if the target application should be started if it is not running yet when the button is pressed. For example it would not make sense for actions that should close an application to launch it. The third and last option for actions is to define which instance of an application should receive the action if there are more then on instances running. If you have selected an application that cannot be run multiple times this option is disabled.


Options for actions

Actions may also be automatically populated using the wizard button. This means that KRemoteControl can attempt to match buttons to functions for you. The autopopulate dialog shows all available templates collections with a flag. Depending on the color of the flag your remote control is fully, partially or not supported by that profile. Green means all contained templates can be matched to your remote control, yellow means some of the contained actions match and red means none of the templates can be matched to buttons of your remote control. This doesn't mean that you cannot use those templates. You just have to configure them one by one, setting the desired button by yourself.


Automatically generate actions using templates

Note: If your remote control isn't compatible to any profile you might haven't configured LIRC using namespaces.