| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In 2.x, the !HAVE_XCONVERTCASE fallback of keyval_convert_case() was
implicitly used as implementation for all !X11 backends.
In 3.x, when this function was virtualized in GdkDisplayManager,
this fallback was moved to the X11 backend and the other backends
"equipped" with /* FIXME implement */ implementations of
keyval_convert_case() which don't convert anything.
Move the fallback code back to gdk/ as default implementation
of GdkDisplayManager::keyval_convert_case() and remove its
implementations is all backends but X11. Also remove the
implementation in Wayland which was a plain copy of what
is now the default implementation.
(cherry picked from commit f46c1b76d839a03bdc8080bc130fabd1068f2557)
|
|
|
|
|
|
|
| |
Added install commands for the gdk/win32 headers as referenced from
gdkwin32.h.
https://bugzilla.gnome.org/show_bug.cgi?id=653964
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
_gdk_device_get_axis_use() dates back to pre-sealing, when the
xi2 work began, this remaining can be gone with a public
gdk_device_get_axis_use() function already in place.
|
|
|
|
|
|
|
|
|
|
| |
GDK_NATIVE_WINDOWS was a way to keep some old apps running that did weird
things in gtk2. We should not have to carry this forwards in gtk 3.x.
We do however keep a g_warning() call reminding people of this fact to
ease debugging when they try to port their applications.
https://bugzilla.gnome.org/show_bug.cgi?id=644119
|
|
|
|
| |
Mostly correcting it's to its and changing some , to .
|
|
|
|
|
| |
wintab.h defines an INT() macro that interfers with some lines in
commctrl.h.
|
|
|
|
|
| |
Fixes bug #642772. Thanks to the anonymous bug reporter for providing
a test program.
|
|
|
|
|
|
| |
- replace GdkNativeWindow with HWND, remove type casts
- no more GdkDisplayClass::get_drag_protocol but GdkWindowImpl::get_drag_protocol
- remove *_client_message*()
|
| |
|
|
|
|
| |
We don't have colormaps anymore.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
There are sure regressions but basic stuff seems to be working
again after all the API breakage done with comments like
"Win32 and Quartz need to be ported still."
|
|
|
|
|
| |
THe use of this function will become visible in the next commits. But
wrapping g_object_new() is a generally a good idea anyway.
|
|
|
|
| |
Now that we store the display inside the cursor, that change is obvious.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This commit hides the GdkDisplayManager instance and class structs,
adds vfuncs for listing displays, opening displays, and getting and
setting the default display. The X11 backend has a derived
GdkDisplayManagerX11.
The gdk_display_manager_get() function is responsible for deciding on
which of the compiled in backends to use. Currently, it consults the
GDK_BACKEND environment variable and falls back to x11.
|
|
|
|
| |
All backends updated.
|
| |
|
|
|
|
|
|
|
|
|
| |
This commit hides GdkDragContext and GdkDragContextClass, adds
vfuncs for most drag context functionality, and turns the X11 DND
implementation into GdkDragContextX11. We also add vfuncs to
GdkDisplay for gdk_drag_get_protocol and to GdkWindow for
gdk_drag_begin, and implemenet them for X11.
Other backends need similar treatment and are broken now.
|
|
|
|
|
|
|
|
|
| |
Add a GdkDisplay::get_app_launch_context vfunc, and a
gdk_display_get_app_launch_context that for X11 returns a subclass.
For win32 and quartz, the implementations were trivial, so we
just return a new GdkAppLaunchContext without subclassing. Since
the type of the context now depends on the display,
gdk_app_launch_context_set_display is deprecated.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
For now that function just calls the event func.
|
|
|
|
|
|
|
|
| |
One less magic function. Also refactored it to make it easier to
implement. It now returns TRUE if it beeped and FALSE if it failed to do
so. A default implementation exists that just returns FALSE for all the
backends that can't beep windows (read: everything but X11 with XKB -
and why on earth do keyboard libs implement beeping?)
|
|
|
|
|
|
| |
Trying to get rid of all the _gdk_windowing_something() functions that
we expect backends to magically know about and instead put them in a
proper interface (mostly GdkWindowImplClass).
|
|
|
|
| |
It's not used by anyone and not supported by any backend but X11.
|
|
|
|
| |
So it's in sync with all the other vfuncs.
|
|
|
|
|
| |
It was only used in the backends, and they can use the correct type
directly.
|
|
|
|
| |
We're not passing a GdKWindow here, but the implementation.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
An event filter may add or remove filters itself. This patch does
two things to address this case. The first is to take a temporary
reference to the filter while it is being used. The second is
to wait until after the filter function is run before determining
the next node in the list to process. This guards against
changes to the next node. It also does not run functions
that have been marked as removed. Though I'm not sure if this
case can arise.
https://bugzilla.gnome.org/show_bug.cgi?id=635380
|
|
|
|
|
|
| |
Otherwise the blink timeout is the one used by default in GTK+.
https://bugzilla.gnome.org/show_bug.cgi?id=634697
|
| |
|
| |
|
|
|
|
| |
"n_events" went back from guint to gint.
|
| |
|
|
|
|
|
| |
Note the special implementation of this method on GdkOffscreenWindow
that makes sure its current surface is not destroyed.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
In particular, the following functions are gone:
- gdk_screen_get_default_colormap()
- gdk_screen_set_default_colormap()
- gdk_screen_get_system_colormap()
- gdk_screen_get_rgba_colormap()
|