- 30 Apr, 2018 5 commits
-
-
Benjamin Otte authored
Link libgtk to libintl See merge request GNOME/gtk!113
-
Benjamin Otte authored
Resolve "GtkTextView accesses already disposed object" Closes #169 See merge request GNOME/gtk!109
-
-
Benjamin Otte authored
gdk: do not deactivate surface on keyboard grab Closes #85 See merge request GNOME/gtk!120
-
Samuel Thibault authored
When pressing e.g. a window manager shortcut, which acquires keyboard grab, Xorg would send FocusOut NotifyGrab then FocusIn NotifyUngrab. Currently gdk would then deactivate the current surface, which makes accessibility screen readers think that we have switched to a non-accessible application and came back again, and thus reannounce the application frame etc. which we don't want when e.g. just raising volume. And actually, receiving FocusOut NotifyGrab does not mean losing the X focus, it only means an application aqcuired a grab, i.e. it is temporarily stealing keyboard events. On Wayland, this isn't even notified actually. This commit makes gdk only deactivate surfaces when there was an actual focus switch to another window, as determined by has_focus_window (instead of just has_focus), which happens either normally through FocusOut with NotifyNormal, or during grabs through FocusOut with NotifyWhileGrabbed. Fixes #85
-
- 29 Apr, 2018 1 commit
-
-
Matthias Clasen authored
Close some gaps in gdk docs.
-
- 28 Apr, 2018 6 commits
-
-
Matthias Clasen authored
-
Matthias Clasen authored
If only the errors would make it back to stderr.
-
Matthias Clasen authored
-
Matthias Clasen authored
-
Matthias Clasen authored
GdkDrawingContext no longer exists.
-
-
- 27 Apr, 2018 4 commits
-
-
Benjamin Otte authored
Also remove gdk_drag_context_set_device() and insist on backends using the property.
-
Benjamin Otte authored
Instead of creating and reusing the same one from start to finish.
-
Benjamin Otte authored
Otherwise buttons don't work as drag sources, and we like to do that.
-
Benjamin Otte authored
When changing the widget type, don't start out with 0 icons.
-
- 26 Apr, 2018 4 commits
-
-
-
LRN authored
gdk_win32_keymap_check_compose() shouldn't be called for non-W32 displays (i.e. when using broadway or other backends that could be made to run on Windows).
-
to retreive paper size specific hard margins and use this to set the hard margins in the print context. (modified by Marek Kasik <mkasik@redhat.com>) https://bugzilla.gnome.org/show_bug.cgi?id=686109
-
-
- 25 Apr, 2018 6 commits
-
-
Carlos Garnacho authored
The function hooked up to the ::key-pressed signal should have a return value. Pointed out by Peter Bloomfield.
-
Benjamin Otte authored
What you don't find when laughing at vcpkg having a CMake build file for GTK.
-
Daniel Mustieles authored
-
Carlos Garnacho authored
gtk_get_current_event() returns a new reference to the event, it should be freed across various return branches to avoid the event leak, or we just fetch the little stuff we're interested in.
-
Carlos Garnacho authored
Prevents keybindings from working on scales.
-
Carlos Garnacho authored
Prevents combobox menus from being closed.
-
- 24 Apr, 2018 14 commits
-
-
Benjamin Otte authored
Now that all Cairo contexts are ported to managing cairo surfaces themselves, the old fallback code that didi the managing is no longer needed. Also clarify the behavior of gdk_cairo_context_cairo_create() wrt the vfunc by doing the early exit and the clipping outside of it.
-
LRN authored
* Remove DC refcounting (we trust GDK to always do begin_frame/end_frame calls in pairs) * Now that there's no GDK-provided double-buffer up the stack, double-buffering is implemented here (though it's disabled by default - in my tests it didn't provide any visual improvements, but did decrease performance). * For some reason delaying window resizes until the point where we need to blit the double-buffer into the window leads to visual glitches, so doulbe-buffered windows are resized in begin_frame, same as non-double-buffered ones. * New code to clear the paint region, for all drawing modes. Hopefully, it isn't duplicated anywhere up the stack. * GL has its own context now, so remove any GL-related comments. * Layered windows are still used (because cairo actually works better with them) * A bit more code re-use for layered windows * Some functions that were local to gdksurface-win32.c are made usable for the whole backend * Drag-indicator drawing is temporarily commented out to match a similar change in X11 backend
-
Alexander Larsson authored
-
Alexander Larsson authored
-
Alexander Larsson authored
-
Alexander Larsson authored
-
Alexander Larsson authored
-
Benjamin Otte authored
We used to pass 2 regions to GdkDrawCotnext.end_frame() but code was confusing what they meant. So we now don't do that anymore and only pass the region that matters: The frame region.
-
Benjamin Otte authored
This makes the previous gdk_draw_context_is_drawing() function public under a new name. I decided against the old name because we use the term "frame" for a drawing operation, so I wanted to have this boolean flag reuse the term.
-
Benjamin Otte authored
... and get rid of duplicate variable in the process.
-
Benjamin Otte authored
As they require a draw context and the draw context is already bound to the surface, it makes much more sense and reduces abiguity by moving these APIs to the draw context. As a side effect, we simplify GdkSurface APIs to a point where GdkSurface now does not concern itself with drawing anymore at all, apart from being the object that creates draw contexts.
-
Benjamin Otte authored
All information is kept in GdkDrawContext these days, so use that one.
-
Benjamin Otte authored
Use the identical gdk_draw_context_get_frame_region() instead.
-
Benjamin Otte authored
This does the same as gdk_drawing_context_get_clip().
-