Sets our main struct and passes it to the parent class.
Creates a new gtk.PadController that will associate events from pad to actions. A NULL pad may be provided so the controller manages all pad devices generically, it is discouraged to mix gtk.PadController objects with NULL and non-NULL pad argument on the same window, as execution order is not guaranteed.
Get the main Gtk struct
the main Gtk struct as a void*
Adds an individual action to controller. This action will only be activated if the given button/ring/strip number in index is interacted while the current mode is mode. -1 may be used for simple cases, so the action is triggered on all modes.
This is a convenience function to add a group of action entries on controller. See GtkPadActionEntry and Pad.controllerSetAction.
the main Gtk struct
the main Gtk struct
Get the main Gtk struct
the main Gtk struct as a void*
Gets the propagation phase at which controller handles events.
Returns the gtk.Widget this controller relates to.
Feeds an events into controller, so it can be interpreted and the controller actions triggered.
Resets the controller to a clean state. Every interaction the controller did through handle-event will be dropped at this point.
Sets the propagation phase at which a controller handles events.
gtk.PadController is an event controller for the pads found in drawing tablets (The collection of buttons and tactile sensors often found around the stylus-sensitive area).
These buttons and sensors have no implicit meaning, and by default they perform no action, this event controller is provided to map those to gtk.Action objects, thus letting the application give those a more semantic meaning.
Buttons and sensors are not constrained to triggering a single action, some GDK_SOURCE_TABLET_PAD devices feature multiple "modes", all these input elements have one current mode, which may determine the final action being triggered. Pad devices often divide buttons and sensors into groups, all elements in a group share the same current mode, but different groups may have different modes. See Device.padGetNGroups and Device.padGetGroupNModes.
Each of the actions that a given button/strip/ring performs for a given mode is defined by GtkPadActionEntry, it contains an action name that will be looked up in the given gtk.ActionGroup and activated whenever the specified input element and mode are triggered.
A simple example of gtk.PadController usage, assigning button 1 in all modes and pad devices to an "invert-selection" action: |[ GtkPadActionEntry *pad_actions[] = { { GTK_PAD_ACTION_BUTTON, 1, -1, "Invert selection", "pad-actions.invert-selection" }, … };
… action_group = g_simple_action_group_new (); action = g_simple_action_new ("pad-actions.invert-selection", NULL); g_signal_connect (action, "activate", on_invert_selection_activated, NULL); g_action_map_add_action (G_ACTION_MAP (action_group), action); … pad_controller = gtk_pad_controller_new (window, action_group, NULL);