Skip to content

Instructions

dterrahe edited this page Jun 1, 2021 · 2 revisions

To visually create shortcuts, switch to shortcut mapping mode by clicking the button to the left of the global settings "gear" button.

Now, the mouse cursor will indicate what actions are available.

  • a generic cross when there is no mappable widget under the cursor. Clicking the left mouse button will call up the shortcuts configuration dialog (where you can configure shortcuts for non-visual actions).
  • A spiral cursor if a shortcut can be defined for the widget under the cursor.
  • a double up arrow if in addition to assigning a shortcut, you can also add the widget to the Quick Access Panel in the darkroom (by ctrl+clicking on it)
  • a double down arrow if the widget is already in the quick access panel (ctrl+click will remove it).

Exit shortcut mapping mode by right clicking anywhere or by clicking the define shortcuts button again.

To assign a simple shortcut to a widget, hover over it in mapping mode and press a key. The same widget can have multiple shortcuts (either with different settings or from different devices) so creating a new shortcut does not delete/overwrite an existing one. If the shortcut is already used elsewhere, you are asked if you want to reassign it. If you assign the same shortcut to the same widget, you are asked if you want to remove it.

More complex shortcuts can be created. All start at least with a keypress, unless they are coming from an external device such as a midi or gamepad controller.

Different components that can be used in a shortcut are:

  • modifier keys (ctrl, shift, alt)
  • multiple/long presses; a key can be double/triple pressed and the last press can be long. A long press cannot be combined with any of the following options (because the key needs to be released to "end" the long press).
  • mouse clicks; combinations of left/middle/right buttons can have different meanings.
  • multiple/long clicks; similar to presses above.
  • mouse wheel scroll
  • mouse moves (horizontal, vertical or diagonally) External devices (midi/gamepad) can provide different moves, for example knob turns or joystick moves. These will be registered even if no (keyboard or device) keys are pressed first.

After a shortcut has been assigned this way, it will trigger a default action when it is used in non-mapping mode. For a scroll wheel move assigned to a slider, this means it will change the slider value. For a key assigned to a button, it will "press" the button. However, these defaults can be changed in the shortcuts configuration dialog. It opens when (left) clicking anywhere while in mapping mode. If you click on a mappable widget, it will filter all the shortcuts currently assigned to that widget. You can remove, or change, the filter by clicking on the selected action in the bottom half of the dialog.

Now you can change

  • The speed of a scroll wheel turn (on a per widget basis; you can even use a negative value).
  • Or you can change the element of the widget that is affected by the shortcut; for a slider that has a color picker, you can make a key press activate the color picker. For a row of notebook tabs (which is one widget) you can select which tab to activate. A slider has a normal "value" element, but if you don't want to be constrained by the currently active soft limits, you can chose the "force" element.
  • An element may list several different _effect_s a shortcut can have on it, which can be selected in the configuration dialog. A button for example can be activated normally, or as if it was pressed while holding ctrl (its tooltip will probably tell what impact that would have). Normally a key or button (double/triple/long) press/click would default to the first effect, while an up/down scroll or move would trigger the 2nd or 3rd effect. A slider will default to having its popup editor appear, but can also be reset or set to its maximum or minimum value.
  • For widgets in an image processing module you can indicate which instance of the module (if there are multiple instances) will be affected. Either the instance that currently has the focus, or is otherwise preferred as per the rules in the preferences dialog, or the 1st, 2nd etc either from the bottom or the top of the list.

Clone this wiki locally