- 18 Mar, 2022 1 commit
-
-
panoplie authored
Add a new GdkScrollUnit enum that represent the unit of scroll deltas provided by GdkScrollEvent. The unit is accessible through gdk_scroll_event_get_unit().
-
- 26 Jan, 2022 1 commit
-
-
Allow to create hold events as well as the required functions to get information about the event: gesture phase, finger count, etc Part-of: <!3454>
-
- 26 Oct, 2021 1 commit
-
-
Benjamin Otte authored
Add gdkenums.h for enums and keep gdktypes.h for types. Makes both files easier to read.
-
- 20 May, 2021 1 commit
-
-
Matthias Clasen authored
Mostly fixing up indentation of continuation lines, and other small cleanups.
-
- 11 Mar, 2021 2 commits
-
-
Emmanuele Bassi authored
Drop the `:`.
-
Convert links, make things more concise.
-
- 07 Dec, 2020 1 commit
-
-
Jonas Ådahl authored
This removes the GDK_CONFIGURE event and all related functions and data types; it includes untested changes to the MacOSX, Win32 and Broadway backends.
-
- 12 Sep, 2020 1 commit
-
-
Matthias Clasen authored
Replace most remaining uses of GTK+ in the docs and user-visible strings by GTK. Also remove some leftover "Was added in 3.x" sentences from the docs.
-
- 05 Aug, 2020 1 commit
-
-
Matthias Clasen authored
Clean up references to no-longer-existing APIs.
-
- 28 Jul, 2020 1 commit
-
-
Carlos Garnacho authored
Make GdkEvents hold a single GdkDevice. This device is closer to the logical device conceptually, although it must be sufficient for device checks (i.e. GdkInputSource), which makes it similar to the physical devices. Make the logical devices have a more accurate GdkInputSource where needed, and conflate the event devices altogether.
-
- 23 Jun, 2020 1 commit
-
-
Carlos Garnacho authored
It currently fetches the seat from the event device, will be changed in future commits.
-
- 09 Jun, 2020 2 commits
-
-
Matthias Clasen authored
Scroll events can have history too, so make a getter that works for both. This drops the gdk_scroll_event_get_history getter that was added a few commits earlier, since we now store scroll history in the same way as motion history. Update the docs, and all callers.
-
Matthias Clasen authored
Similar to how we keep motion history for compressed events, keep scroll history for compressed scroll events.
-
- 05 May, 2020 1 commit
-
-
Timm Bäder authored
Instead of a less efficient GList.
-
- 16 Apr, 2020 1 commit
-
-
Emmanuele Bassi authored
GdkEvent has been a "I-can't-believe-this-is-not-OOP" type for ages, using a union of sub-types. This has always been problematic when it comes to implementing accessor functions: either you get generic API that takes a GdkEvent and uses a massive switch() to determine which event types have the data you're looking for; or you create namespaced accessors, but break language bindings horribly, as boxed types cannot have derived types. The recent conversion of GskRenderNode (which had similar issues) to GTypeInstance, and the fact that GdkEvent is now a completely opaque type, provide us with the chance of moving GdkEvent to GTypeInstance, and have sub-types for GdkEvent. The change from boxed type to GTypeInstance is pretty small, all things considered, but ends up cascading to a larger commit, as we still have backends and code in GTK trying to access GdkEvent structures directly. Additionally, the naming of the public getter functions requires renaming all the data structures to conform to the namespace/type-name pattern.
-
- 06 Apr, 2020 3 commits
-
-
Matthias Clasen authored
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.
-
Matthias Clasen authored
This is a counterpart to gdk_event_matches() that can be used to obtain a shortcut matching an event.
-
Matthias Clasen authored
Move the elaborate key event matching code from GtkShortcutTrigger to GdkEvent, which greatly reduces the amount of keymap api use outside of GDK.
-
- 21 Feb, 2020 10 commits
-
-
Matthias Clasen authored
All events are GdkEvents now.
-
Matthias Clasen authored
-
Matthias Clasen authored
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.
-
Matthias Clasen authored
We don't need a separate api to turn on debugging for events.
-
Matthias Clasen authored
Events are refcounted structs, and we generally don't pass these as const.
-
Matthias Clasen authored
GdkEvent is now truly readonly.
-
Matthias Clasen authored
Events of type GDK_NOTHING are good for nothing.
-
Matthias Clasen authored
-
Matthias Clasen authored
These functions are no longer used outside of gdkevents.c.
-
Matthias Clasen authored
No backend is emitting GDK_DESTROY events anymore, so no need to carry this around.
-
- 27 Nov, 2019 1 commit
-
-
Emmanuele Bassi authored
We use a compilation symbol in our build to allow the inclusion of specific headers while building GTK, to avoid the need to include only the global header. Each namespace has its own compilation symbol because we used to have different libraries, and strict symbol visibility between libraries; now that we have a single library, and we can use private symbols across namespaces while building GTK, we should have a single compilation symbol, and simplify the build rules.
-
- 31 May, 2019 1 commit
-
-
Matthias Clasen authored
-
- 28 May, 2019 1 commit
-
-
Matthias Clasen authored
Drop gdk_surface_child_new and the child surface type, since we no longer use them. Deprecate surface apis that only make sense with child surfaces.
-
- 23 Feb, 2019 1 commit
-
-
Matthias Clasen authored
This is no longer used by GTK.
-
- 18 Jan, 2019 1 commit
-
-
Timm Bäder authored
-
- 22 Dec, 2018 1 commit
-
-
g-ir-scanner incorrectly evaluates macro definition that include references to other macro definitions. Provide a correct value as an annotation. Differences in generated gir files: ```diff @@ -19017 +19017 @@ - <constant name="PRIORITY_REDRAW" value="20" c:type="GDK_PRIORITY_REDRAW"> + <constant name="PRIORITY_REDRAW" value="120" c:type="GDK_PRIORITY_REDRAW"> @@ -74229,3 +74229,3 @@ </constant> - <constant name="PRIORITY_RESIZE" value="10" c:type="GTK_PRIORITY_RESIZE"> + <constant name="PRIORITY_RESIZE" value="110" c:type="GTK_PRIORITY_RESIZE"> <doc xml:space="preserve">Use this priority for functionality related to size allocation. @@ -106786,3 +106786,3 @@ <constant name="TEXT_VIEW_PRIORITY_VALIDATE" - value="5" + value="125" c:type="GTK_TEXT_VIEW_PRIORITY_VALIDATE"> ``` See !472
-
- 30 Jul, 2018 1 commit
-
-
Benjamin Otte authored
You want to use an IM module to get strings out of keypresses, not some crude hack that only works on X11 and Wayland anyway.
-
- 16 Jul, 2018 1 commit
-
-
Matthias Clasen authored
This reverts commit a8926c9d.
-
- 15 Jul, 2018 3 commits
-
-
Matthias Clasen authored
We are really inconsistent about generating these, and they are not actually used in GTK+. Instead, add a boolean GdkSurface::mapped property.
-
Matthias Clasen authored
Replace expose events with a GdkSurface::expose signal. This is part of the move to use events only for input.
-
Matthias Clasen authored
Replace configure events with a GdkSurface::size-changed signal. This is part of the move to use events only for input.
-
- 02 Jul, 2018 1 commit
-
-
Matthias Clasen authored
Rename gdkdnd.h to gdkdrag.h, to go along with gdkdrop.h This commit includes the necessary updates to the X11, Wayland and Broadway backends. Other backends have to be updated separately.
-