summaryrefslogtreecommitdiff
path: root/ChangeLog.pre-2-0
diff options
context:
space:
mode:
authorOwen Taylor <otaylor@redhat.com>1999-01-12 23:27:30 +0000
committerOwen Taylor <otaylor@src.gnome.org>1999-01-12 23:27:30 +0000
commit24f6d8b887ffdd24e1841340c81b54e41811e165 (patch)
treea320b3efe6053ceb3d4e17e06d515f0d943fd989 /ChangeLog.pre-2-0
parent5a86cbd116bd55fbb31b3c90baca8cd30dd395d0 (diff)
downloadgtk+-24f6d8b887ffdd24e1841340c81b54e41811e165.tar.gz
Add a drag_data_received handler for the label.
Tue Jan 12 18:30:51 1999 Owen Taylor <otaylor@redhat.com> * gtk/testdnd.c (label_drag_data_received): Add a drag_data_received handler for the label. Tue Jan 12 15:01:50 1999 Owen Taylor <otaylor@redhat.com> * gdk/gdkevents.c: Removed the putback_events queue, since it was causing problems with event ordering - just keep a single queue. If we need it, we can add priorities to events. * gdk/gdkevents.c: Annotate events with flags - we allocate a GdkEventPrivate structure in gdk_event_new() and use these flags to mark an event being translated as "pending" - I.e., not yet ready to be dequeued. So we can put the event on the queue and get the order of the events right. (This solves the double-click problems) * gdk/gdk.h gdk/gdkevents.h: Add gdk_event_peek() to get a copy of the next event on the event queue. * gtk/gtkmain.c (gtk_main_do_event): Use gdk_event_peek() to check the next event without causing event queue reordering.
Diffstat (limited to 'ChangeLog.pre-2-0')
-rw-r--r--ChangeLog.pre-2-026
1 files changed, 26 insertions, 0 deletions
diff --git a/ChangeLog.pre-2-0 b/ChangeLog.pre-2-0
index f7a6ea3bff..0dd7d9af51 100644
--- a/ChangeLog.pre-2-0
+++ b/ChangeLog.pre-2-0
@@ -1,3 +1,29 @@
+Tue Jan 12 18:30:51 1999 Owen Taylor <otaylor@redhat.com>
+
+ * gtk/testdnd.c (label_drag_data_received): Add
+ a drag_data_received handler for the label.
+
+Tue Jan 12 15:01:50 1999 Owen Taylor <otaylor@redhat.com>
+
+ * gdk/gdkevents.c: Removed the putback_events queue,
+ since it was causing problems with event ordering -
+ just keep a single queue. If we need it, we can
+ add priorities to events.
+
+ * gdk/gdkevents.c: Annotate events with flags - we allocate
+ a GdkEventPrivate structure in gdk_event_new() and use these
+ flags to mark an event being translated as "pending" -
+ I.e., not yet ready to be dequeued. So we can put
+ the event on the queue and get the order of the
+ events right. (This solves the double-click problems)
+
+ * gdk/gdk.h gdk/gdkevents.h: Add gdk_event_peek() to get a copy
+ of the next event on the event queue.
+
+ * gtk/gtkmain.c (gtk_main_do_event): Use gdk_event_peek()
+ to check the next event without causing event queue
+ reordering.
+
Tue Jan 12 15:41:20 1999 Owen Taylor <otaylor@redhat.com>
* gtk/gtklabel.c (gtk_label_expose): Minor fix