mirror of
https://gitlab.gnome.org/GNOME/gtk.git
synced 2024-12-30 15:31:34 +00:00
f0d04f82f8
1) Ensure that any DELETE requests from the target are sent to GDK, even if both the source and the target are in the same process and it is therefore possible to use a shortcut and call the handler directly in GTK layer 2) Ensure that target GDK doesn't do anything when GTK asks it to send a DELETE request, just report back immediately (the code up the stack does not check for successfullness when request is DELETE, so not giving it any data is OK). The source code already synthesizes a DELETE request, so that side is also taken care of. https://bugzilla.gnome.org/show_bug.cgi?id=786509 |
||
---|---|---|
.. | ||
rc | ||
bdfcursor.c | ||
cursor.bdf | ||
gdkcursor-win32.c | ||
gdkdevice-virtual.c | ||
gdkdevice-virtual.h | ||
gdkdevice-win32.c | ||
gdkdevice-win32.h | ||
gdkdevice-wintab.c | ||
gdkdevice-wintab.h | ||
gdkdevicemanager-win32.c | ||
gdkdevicemanager-win32.h | ||
gdkdisplay-win32.c | ||
gdkdisplay-win32.h | ||
gdkdisplaymanager-win32.c | ||
gdkdnd-win32.c | ||
gdkevents-win32.c | ||
gdkgeometry-win32.c | ||
gdkglcontext-win32.c | ||
gdkglcontext-win32.h | ||
gdkglobals-win32.c | ||
gdkkeys-win32.c | ||
gdkmain-win32.c | ||
gdkmonitor-win32.c | ||
gdkmonitor-win32.h | ||
gdkprivate-win32.h | ||
gdkproperty-win32.c | ||
gdkscreen-win32.c | ||
gdkselection-win32.c | ||
gdkselection-win32.h | ||
gdkvulkancontext-win32.c | ||
gdkvulkancontext-win32.h | ||
gdkwin32.h | ||
gdkwin32cursor.h | ||
gdkwin32display.h | ||
gdkwin32displaymanager.h | ||
gdkwin32dnd-private.h | ||
gdkwin32dnd.h | ||
gdkwin32glcontext.h | ||
gdkwin32id.c | ||
gdkwin32keys.h | ||
gdkwin32misc.h | ||
gdkwin32monitor.h | ||
gdkwin32screen.h | ||
gdkwin32window.h | ||
gdkwindow-win32.c | ||
gdkwindow-win32.h | ||
libwntab32x.la | ||
meson.build | ||
pktdef.h | ||
wintab.h | ||
xcursors.h |