Event timestamps don't have to be unique. As long as they are
2004-11-10 Tor Lillqvist <tml@iki.fi> * gdk/win32/gdkevents-win32.c (_gdk_win32_get_next_tick): Event timestamps don't have to be unique. As long as they are nondecreasing we should be fine. Solves problems with for instance long menus not staying up on first click. (#152035, Robert Ögren)
This commit is contained in:
committed by
Tor Lillqvist
parent
1b20880913
commit
1a7ead495f
@@ -1,3 +1,10 @@
|
||||
2004-11-10 Tor Lillqvist <tml@iki.fi>
|
||||
|
||||
* gdk/win32/gdkevents-win32.c (_gdk_win32_get_next_tick):
|
||||
Event timestamps don't have to be unique. As long as they are
|
||||
nondecreasing we should be fine. Solves problems with for instance
|
||||
long menus not staying up on first click. (#152035, Robert Ögren)
|
||||
|
||||
2004-11-08 Matthias Clasen <mclasen@redhat.com>
|
||||
|
||||
* gtk/gtkaction.c (_gtk_action_sync_menu_visible): Use
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
2004-11-10 Tor Lillqvist <tml@iki.fi>
|
||||
|
||||
* gdk/win32/gdkevents-win32.c (_gdk_win32_get_next_tick):
|
||||
Event timestamps don't have to be unique. As long as they are
|
||||
nondecreasing we should be fine. Solves problems with for instance
|
||||
long menus not staying up on first click. (#152035, Robert Ögren)
|
||||
|
||||
2004-11-08 Matthias Clasen <mclasen@redhat.com>
|
||||
|
||||
* gtk/gtkaction.c (_gtk_action_sync_menu_visible): Use
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
2004-11-10 Tor Lillqvist <tml@iki.fi>
|
||||
|
||||
* gdk/win32/gdkevents-win32.c (_gdk_win32_get_next_tick):
|
||||
Event timestamps don't have to be unique. As long as they are
|
||||
nondecreasing we should be fine. Solves problems with for instance
|
||||
long menus not staying up on first click. (#152035, Robert Ögren)
|
||||
|
||||
2004-11-08 Matthias Clasen <mclasen@redhat.com>
|
||||
|
||||
* gtk/gtkaction.c (_gtk_action_sync_menu_visible): Use
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
2004-11-10 Tor Lillqvist <tml@iki.fi>
|
||||
|
||||
* gdk/win32/gdkevents-win32.c (_gdk_win32_get_next_tick):
|
||||
Event timestamps don't have to be unique. As long as they are
|
||||
nondecreasing we should be fine. Solves problems with for instance
|
||||
long menus not staying up on first click. (#152035, Robert Ögren)
|
||||
|
||||
2004-11-08 Matthias Clasen <mclasen@redhat.com>
|
||||
|
||||
* gtk/gtkaction.c (_gtk_action_sync_menu_visible): Use
|
||||
|
||||
@@ -225,7 +225,7 @@ _gdk_win32_get_next_tick (gulong suggested_tick)
|
||||
if (suggested_tick == 0)
|
||||
suggested_tick = GetTickCount ();
|
||||
if (suggested_tick <= cur_tick)
|
||||
return ++cur_tick;
|
||||
return cur_tick;
|
||||
else
|
||||
return cur_tick = suggested_tick;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user