Don't call XTranslateCoordinates on a destroyed window. (Why do we do

Fri Mar 27 21:01:17 1998  Owen Taylor  <owt1@cornell.edu>

	* gdk/gdk.c (gdk_event_translate): Don't call
	XTranslateCoordinates on a destroyed window. (Why do we
	do event processing at all on destroyed windows when we
	throw out the results?)

	* gtk/gtklabel.c: Clear the background when changing style/
	state.
This commit is contained in:
Owen Taylor 1998-03-28 02:08:27 +00:00 committed by Owen Taylor
parent 7033e33822
commit 5b3cc69b43
9 changed files with 74 additions and 2 deletions

View File

@ -1,3 +1,13 @@
Fri Mar 27 21:01:17 1998 Owen Taylor <owt1@cornell.edu>
* gdk/gdk.c (gdk_event_translate): Don't call
XTranslateCoordinates on a destroyed window. (Why do we
do event processing at all on destroyed windows when we
throw out the results?)
* gtk/gtklabel.c: Clear the background when changing style/
state.
Fri Mar 27 16:35:00 PST 1998 Shawn T. Amundson <amundson@gtk.org>
* Released GTK+ 0.99.9

View File

@ -1,3 +1,13 @@
Fri Mar 27 21:01:17 1998 Owen Taylor <owt1@cornell.edu>
* gdk/gdk.c (gdk_event_translate): Don't call
XTranslateCoordinates on a destroyed window. (Why do we
do event processing at all on destroyed windows when we
throw out the results?)
* gtk/gtklabel.c: Clear the background when changing style/
state.
Fri Mar 27 16:35:00 PST 1998 Shawn T. Amundson <amundson@gtk.org>
* Released GTK+ 0.99.9

View File

@ -1,3 +1,13 @@
Fri Mar 27 21:01:17 1998 Owen Taylor <owt1@cornell.edu>
* gdk/gdk.c (gdk_event_translate): Don't call
XTranslateCoordinates on a destroyed window. (Why do we
do event processing at all on destroyed windows when we
throw out the results?)
* gtk/gtklabel.c: Clear the background when changing style/
state.
Fri Mar 27 16:35:00 PST 1998 Shawn T. Amundson <amundson@gtk.org>
* Released GTK+ 0.99.9

View File

@ -1,3 +1,13 @@
Fri Mar 27 21:01:17 1998 Owen Taylor <owt1@cornell.edu>
* gdk/gdk.c (gdk_event_translate): Don't call
XTranslateCoordinates on a destroyed window. (Why do we
do event processing at all on destroyed windows when we
throw out the results?)
* gtk/gtklabel.c: Clear the background when changing style/
state.
Fri Mar 27 16:35:00 PST 1998 Shawn T. Amundson <amundson@gtk.org>
* Released GTK+ 0.99.9

View File

@ -1,3 +1,13 @@
Fri Mar 27 21:01:17 1998 Owen Taylor <owt1@cornell.edu>
* gdk/gdk.c (gdk_event_translate): Don't call
XTranslateCoordinates on a destroyed window. (Why do we
do event processing at all on destroyed windows when we
throw out the results?)
* gtk/gtklabel.c: Clear the background when changing style/
state.
Fri Mar 27 16:35:00 PST 1998 Shawn T. Amundson <amundson@gtk.org>
* Released GTK+ 0.99.9

View File

@ -1,3 +1,13 @@
Fri Mar 27 21:01:17 1998 Owen Taylor <owt1@cornell.edu>
* gdk/gdk.c (gdk_event_translate): Don't call
XTranslateCoordinates on a destroyed window. (Why do we
do event processing at all on destroyed windows when we
throw out the results?)
* gtk/gtklabel.c: Clear the background when changing style/
state.
Fri Mar 27 16:35:00 PST 1998 Shawn T. Amundson <amundson@gtk.org>
* Released GTK+ 0.99.9

View File

@ -1,3 +1,13 @@
Fri Mar 27 21:01:17 1998 Owen Taylor <owt1@cornell.edu>
* gdk/gdk.c (gdk_event_translate): Don't call
XTranslateCoordinates on a destroyed window. (Why do we
do event processing at all on destroyed windows when we
throw out the results?)
* gtk/gtklabel.c: Clear the background when changing style/
state.
Fri Mar 27 16:35:00 PST 1998 Shawn T. Amundson <amundson@gtk.org>
* Released GTK+ 0.99.9

View File

@ -2556,7 +2556,8 @@ gdk_event_translate (GdkEvent *event,
event->configure.height = xevent->xconfigure.height;
if (!xevent->xconfigure.x &&
!xevent->xconfigure.y)
!xevent->xconfigure.y &&
!window_private->destroyed)
{
gint tx = 0;
gint ty = 0;

View File

@ -2556,7 +2556,8 @@ gdk_event_translate (GdkEvent *event,
event->configure.height = xevent->xconfigure.height;
if (!xevent->xconfigure.x &&
!xevent->xconfigure.y)
!xevent->xconfigure.y &&
!window_private->destroyed)
{
gint tx = 0;
gint ty = 0;