AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity

range: Don't perform a GTK+ grab

Browse Source 
The implicit grab on priv->event_window already warrants that this
widget is the only one getting events while the button is pressed,
so avoid the extra GTK+ grab here.
This commit is contained in:
Carlos Garnacho 2012-01-05 00:27:57 +01:00 committed by Matthias Clasen
parent ce23d52592
commit 170b391e74
1 changed files with 5 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
gtk/gtkrange.c
View File

@ -2347,15 +2347,11 @@ range_grab_add (GtkRange *range,
if (device == priv->grab_device)
return;
if (priv->grab_device != NULL)
{
g_warning ("GtkRange already had a grab device, releasing device grab");
gtk_device_grab_remove (GTK_WIDGET (range), priv->grab_device);
}
/* we don't actually gdk_grab, since a button is down */
gtk_device_grab_add (GTK_WIDGET (range), device, TRUE);
/* Don't perform any GDK/GTK+ grab here. Since a button
* is down, there's an ongoing implicit grab on
* priv->event_window, which pretty much guarantees this
* is the only widget receiving the pointer events.
*/
priv->grab_location = location;
priv->grab_button = button;
priv->grab_device = device;