| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Rename the private header to follow our naming
conventions, and drop the extra gdkkeys.c file.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
allow-none has been deprecated for a long time
already. Instead use optional and nullable everywhere.
|
|
|
|
|
| |
Mostly fixing up indentation of continuation lines,
and other small cleanups.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
When I removed the 0-termination for the entries for
each keyval, I remove the code initializing the key,
but accidentally left the code that adds it to the
array, so gdk_keymap_get_cached_entries_for_keyval
returns one extra, uninitialized value at the end
of the array. Stop doing that.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We currently calling gdk_display_map_keyval up to
once per key event per shortcut trigger, and that function
does an expensive loop over the entire keymap and
allocates an array. Avoid this by caching the entries
in a single array, and have a lookup table for finding
the entries for a keyval.
To do this, change the GdkKeymap.get_entries_for_keyval
signature, and change the ::keys-changed signal to be
RUN_FIRST, since we want to clear the cache in the class
handler before running signal handlers. These changes are
possible now, since keymaps are no longer public API.
|
|
|
|
|
| |
Since GdkKeymap api is on longer public, move relevant
documentation to the long description.
|
|
|
|
| |
This function is no longer public and no longer used.
|
|
|
|
|
|
|
| |
These are not used anymore.
Drop the vfuncs and their implementations in the
broadway, x11, wayland and win32 backends as well.
|
|
|
|
|
| |
We've hardcoded Mod1 = Alt for a long time, there is
no need to keep the confusing naming around anymore.
|
|
|
|
|
|
|
|
|
|
| |
Restructure the getters for event fields to
be more targeted at particular event types.
Update all callers, and replace all direct
event struct access with getters.
As a side-effect, this drops some unused getters.
|
|
|
|
| |
The string is const, so return it like that.
|
| |
|
|
|
|
|
|
|
| |
If we set c_marshaller manually, then g_signal_newv() will not setup a
va_marshaller for us. However, if we provide c_marshaller as NULL, it will
setup both the c_marshaller (to g_cclosure_marshal_VOID__VOID) and
va_marshaller (to g_cclosure_marshal_VOID__VOIDv) for us.
|
|
|
|
| |
Add another reference to the docs.
|
|
|
|
|
|
| |
Add a reference to the getter to the GdkKeymap::direction-changed
signal docs.
sh: indent: command not found
|
|
|
|
|
|
|
| |
Remove all the old 2.x and 3.x version annotations.
GTK+ 4 is a new start, and from the perspective of a
GTK+ 4 developer all these APIs have been around since
the beginning.
|
|
|
|
| |
Avoid a warning from the introspection scanner.
|
|
|
|
|
| |
These signals are going away, don't mention them in
the docs.
|
|
|
|
|
| |
This is a general pattern we want to follow for all
objects in GDK. Also add a getter.
|
|
|
|
|
| |
Replace all uses of the old function by the new one.
No functional change.
|
|
|
|
|
| |
It is better to use the explicit keymap getter - the
default display may not even use the current gdk backend.
|
|
|
|
| |
We were forgetting this in a few places.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch makes that work using 1 of 2 options:
1. Add all missing enums to the switch statement
or
2. Cast the switch argument to a uint to avoid having to do that (mostly
for GdkEventType).
I even found a bug while doing that: clearing a GtkImage with a surface
did not notify thae surface property.
The reason for enabling this flag even though it is tedious at times is
that it is very useful when adding values to an enum, because it makes
GTK immediately warn about all the switch statements where this enum is
relevant.
And I expect changes to enums to be frequent during the GTK4 development
cycle.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=771826
|
|
|
|
|
| |
The wording here was just awkward: TRUE is returned if... Note that
FALSE is also returned if...
|
|
|
|
| |
This avoids pointless allocations
|
|
|
|
| |
default backend modifiers
|
|
|
|
|
|
|
| |
GdkKeymap already has support for _get_num_lock_state() and
_get_caps_lock_state(). Adding _get_scroll_lock_state() would be good
for completness and some backends (Windows?) could take advantage of
this.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=729834
|
|
|
|
| |
Instead of Return value:
|
|
|
|
|
| |
Without sgml mode, we can't escape /* as /* anymore,
so just switch to // for comments in examples.
|
|
|
|
|
| |
With all element markup gone, it is time to turn off
sgml mode, and get rid of entities as well.
|
| |
|
|
|
|
| |
https://wiki.gnome.org/Design/OS/Typography
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
In most cases, the text itself makes the message clear enough.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=723119
|