| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
<property name="action">action(win.quit)</property> style action
specifications now work for GtkShortcutAction properties.
|
| |
|
|
| |
And hook it up into the GtkBuilder infrastructure.
|
| |
|
|
|
|
|
|
| |
API remains the same, but activation is now done via a
shortcutcontroller.
The code uses a controller with global scope so that the
shortcuts are managed with all the other global shortcuts.
|
| |
|
|
| |
It was using the default display unconditionally.
|
| |
|
|
| |
A parse function should return success or not. So do that.
|
| |
|
|
|
| |
Those are useful for putting triggers in hash tables or getting sorted
output.
|
| | |
|
| | |
|
| |
|
|
| |
For all but the callback action, we can print something useful.
|
| |
|
|
| |
No point in creating objects that just hold empty lists.
|
| |
|
|
|
| |
This way, we can use shortcut_controller_new_for_model() and avoid all
the special casing about run_class.
|
| |
|
|
|
|
|
| |
This is mainly for internal use, but I can't see a reason to not have it
public for people who want to maintain their own lists.
I'm sure gnome-builder will never ever find a way to misuse it.
|
| |
|
|
| |
After all, this controller is a list of shortcuts.
|
| | |
|
| |
|
|
|
|
|
|
| |
When creating shortcuts, there almost always are a trigger and an action
available for use. So make gtk_shortcut_new() take those as arguments.
Also add gtk_shortcut_new_with_arguments() so people can easily pass
those in, too.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Similar to GtkShortcutTrigger, GtkShortCutAction provides all the
different ways to activate a shortcut.
So far, these different ways are supported:
- do nothing
- Call a user-provided callback
- Call gtk_widget_activate()
- Call gtk_widget_mnemonic_activate()
- Emit an action signal
- Activate an action from the widget's action muxer
|
| |
|
|
| |
After the removal of GtkAccelMap, these things are no longer necessary.
|
| |
|
|
|
| |
Now that accel paths are gone, the object managing them isn't needed
anymore either.
|
| |
|
|
|
|
|
| |
It's an outdated technology now that everybody is using GActionGroups.
If somebody wanted to support changeable shortcuts, they'd need to
reintroduce it in another way.
|
| |
|
|
| |
It's not used anymore.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This adds an interface for taking care of shortcut controllers with
managed scope.
Only GtkWindow currently implements this interface, so we need to ensure
that we check if any top-level widget we reach is a shortcuts manager
before we call into it.
|
| | |
|
| |
|
|
| |
Makes the shortcut call gtk_widget_mnemonic_activate() upon activation.
|
| |
|
|
|
|
|
| |
Mnemonics need to be triggered with help from the controllers (who
determine the modifiers). Support for that has been added, too.
Mnemonics do not use this yet though.
|
| |
|
|
|
| |
So instead of relying on gtk_window_activate_key(), it's now using
proper infrastructure.
|
| |
|
|
|
|
| |
Event controllers should have replaced all of them.
And if they haven't, apps need to fix their code (I'm
looking at you Gimp).
|
| |
|
|
| |
It was only ever supported by keybindings and those are gone now.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Allow setting the scope for a controller. The scope determines at what
point in event propagation the shortcuts will be activated.
Local scope is the usual activation, global scope means that the root
widget activates the shortcuts - ie they are activated at the very
start of event propagation (for global capture events) or the very end
(for global bubble events).
Managed scope so far is unimplemented.
This is supposed to be used to replace accelerators and mnemonics.
|
| |
|
|
| |
Provide a user-presentable string.
|
| | |
|
| |
|
|
|
|
| |
The function lives in gtkaccelgroup.c, so there's no need to have that
call a private function in another source file. Instead, make that
other source file call gtk_accelerator_get_label() instead.
|
| |
|
|
| |
We can just look them up as-needed, no need to cache them.
|
| |
|
|
| |
The whole binding functionality is now handled by shortcuts.
|
| |
|
|
| |
We're going to use shortcuts soon.
|
| |
|
|
|
|
|
| |
The shortcut controllers are limited to same-native,
so we need to duplicate the Tab and arrow key bindings
for focus handling, as well as the Enter bindings for
activation.
|
| | |
|
| |
|
|
| |
Don't just use a value without initializing it.
|
| |
|
|
|
| |
Reorder the event controllers so that key forwarding to the search
entries really happens after shortcut triggering.
|
| |
|
|
|
|
| |
Instead of manualling invoking bindings, we now reorder event
controllers inside the treemenu, so that shortcuts run before the event
forwarding.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
