GNOME Bugzilla – Bug 663444
api thats stuck in core-pointer land
Last modified: 2011-11-05 05:15:10 UTC
gdk_window_begin_resize_drag gdk_window_begin_move_drag gtk_window_begin_resize_drag gtk_window_begin_move_drag These currently just take button+position+timestamp from an event, and then gdk goes and takes a grab on core_pointer. We need variants that take a device.
The following fixes have been pushed: 7644ef1 GtkWindow: Use new begin_resize_drag api 3b152df Wayland: Adapt to GdkWindowImpl api change 810ef68 Broadway: Adapt to GdkWindowImpl API change 6f48f20 Quartz: Adapt to GdkWindowImpl api change 32884e9 win32: Adapt to GdkWindowImpl api change 250d433 Add device-taking variants of begin_resize/move_drag
Created attachment 200730 [details] [review] GtkWindow: Use new begin_resize_drag api We have an event, so the correct thing to do is to pass the device into the function that we are calling. GDK just grew a variant that takes a device, for this purpose.
Created attachment 200731 [details] [review] Wayland: Adapt to GdkWindowImpl api change
Created attachment 200732 [details] [review] Broadway: Adapt to GdkWindowImpl API change
Created attachment 200733 [details] [review] Quartz: Adapt to GdkWindowImpl api change
Created attachment 200734 [details] [review] win32: Adapt to GdkWindowImpl api change
Created attachment 200735 [details] [review] Add device-taking variants of begin_resize/move_drag This was one of the last places where display->core_pointer was used in non-deprecated code paths.