| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Include gtkprivate.h for I_() and glib-i18n.h for
gettext macros.
|
|
|
|
|
|
|
|
| |
Those property features don't seem to be in use anywhere.
They are redundant since the docs cover the same information
and more. They also created unnecessary translation work.
Closes #4904
|
|
|
|
| |
Replace leftover gtk-doc syntax (#Type) with backquotes.
|
|
|
|
|
|
|
|
| |
Remove a boatload of "or %NULL" from nullable parameters
and return values. gi-docgen generates suitable text from
the annotation that we don't need to duplicate.
This adds a few missing nullable annotations too.
|
|
|
|
|
| |
Mostly fixing up indentation of continuation lines,
and other small cleanups.
|
| |
|
| |
|
| |
|
|
|
|
| |
Point out the need to escape <> in xml.
|
|
|
|
| |
Found while running the testsuite under asan.
|
| |
|
|
|
|
|
|
|
|
| |
This broke when the event type check in gdk_key_event_matches
was removed and replaced by a precondition that accepts both
key press and release events.
Add the check in gtk_keyval_trigger_trigger instead.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add all of the keyboard translation results in the key event,
so we can translate the keyboard state at the time the event
is created, and avoid doing state translation at match time.
We actually need to carry two sets of translation results,
since we ignore CapsLock when matching accelerators, in
gdk_event_matches().
At the same time, drop the scancode field - it is only ever
set on win32, and is basically unused in GTK.
Update all callers.
|
|
|
|
|
|
| |
Move the elaborate key event matching code from
GtkShortcutTrigger to GdkEvent, which greatly reduces
the amount of keymap api use outside of GDK.
|
|
|
|
|
| |
Update symbol lists, and add examples for parsing triggers
and actions.
|
|
|
|
| |
This was broken by the shortcuts branch merge.
|
|
|
|
| |
Alternative triggers are separate by a pipe character.
|
|
|
|
|
| |
We don't need to parse the full accelerator format for mnemonic
triggers.
|
|
|
|
|
|
|
|
|
|
|
| |
We're not returning a full reference for GtkNeverTrigger, but we are
returning full references for mnemonic and keyval triggers; this means
we're either going to leak mnemonic and keyval triggers if we consider
this function a "transfer none" one, or we are going to trigger an
assertion failure when finalizing a never trigger, if we consider this
function a "transfer full" one.
Let's be consistent, and always return a full reference to the caller.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The lightweight inheritance mechanism used for GtkShortcutTrigger is not
going to be usable by bindings, because boxed types cannot have derived
types.
We could use GTypeInstance and derive everything from that, like
GParamSpec, but in the end shortcuts are not really a performance
critical paths, unlike CSS values or render nodes.
|
|
|
|
|
|
|
|
| |
Copy the logic from GtkKeyHash for matching key events
to shortcuts.
Adapt shortcuts test to work with the better matching,
by creating more complete key events.
|
|
|
|
|
|
|
| |
Allow GtkShortcutTrigger to return partial matches.
Currently, no triggers produce such results, and
GtkShortcutController treats partial matches like
exact ones.
|
| |
|
|
|
|
| |
And hook it up into the GtkBuilder infrastructure.
|
|
|
|
|
| |
Those are useful for putting triggers in hash tables or getting sorted
output.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Provide a user-presentable string.
|
|
|
|
|
|
|
|
|
| |
And use it.
I just added it to GtkWidget just to show that I can.
The real reason I want it is for gamepad/joystick triggers
in games, so that it becomes possible to select 2 different
triggers (gamepad and keyboard) for the same shortcut.
|
|
|
|
|
| |
Triggers are meant to describe how to trigger a shortcut.
So far only a keyval + modifiers trigger exists.
|
|
|
|
|
| |
This reverts commit 3ac4c76b18cc89a841ce09f0943539f16988fd21, reversing
changes made to 6ec96d2e989d029a303b8b20ec72b86f974c0e87.
|
| |
|
|
|
|
| |
And hook it up into the GtkBuilder infrastructure.
|
|
|
|
|
| |
Those are useful for putting triggers in hash tables or getting sorted
output.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Provide a user-presentable string.
|
|
|
|
|
|
|
|
|
| |
And use it.
I just added it to GtkWidget just to show that I can.
The real reason I want it is for gamepad/joystick triggers
in games, so that it becomes possible to select 2 different
triggers (gamepad and keyboard) for the same shortcut.
|
|
Triggers are meant to describe how to trigger a shortcut.
So far only a keyval + modifiers trigger exists.
|