forked from AuroraMiddleware/gtk
2943bfef46
Prior to this patch, the hotspot would be passed in buffer coordinate space. Where this were ever tested, i.e. in a patched mutter, the server interpreted them incorrectly, which meant it went undiscovered. In the updated mutter patches the incorrect behavior in GTK+ was discovered due to the behavior in mutter was corrected. In the themed cursor case, the dimensions were not correctly scaled either, but this had no negative visible effect because the dimension is only used for reporting damage tracking, and passing a bigger damage region than surface has no negative visible effects. https://bugzilla.gnome.org/show_bug.cgi?id=752616 |
||
---|---|---|
.. | ||
protocol | ||
gdkapplaunchcontext-wayland.c | ||
gdkcursor-wayland.c | ||
gdkdevice-wayland.c | ||
gdkdisplay-wayland.c | ||
gdkdisplay-wayland.h | ||
gdkdnd-wayland.c | ||
gdkeventsource.c | ||
gdkglcontext-wayland.c | ||
gdkglcontext-wayland.h | ||
gdkkeys-wayland.c | ||
gdkprivate-wayland.h | ||
gdkscreen-wayland.c | ||
gdkselection-wayland.c | ||
gdkwayland.h | ||
gdkwaylanddevice.h | ||
gdkwaylanddisplay.h | ||
gdkwaylandglcontext.h | ||
gdkwaylandselection.h | ||
gdkwaylandwindow.h | ||
gdkwindow-wayland.c | ||
Makefile.am | ||
wm-button-layout-translation.c | ||
wm-button-layout-translation.h |