AuroraMiddleware/gtk
1
0
Fork 1
mirror of https://gitlab.gnome.org/GNOME/gtk.git synced 2024-11-10 10:50:10 +00:00
Code Issues Projects Releases Wiki Activity

put the warning explaining the validation error in front of the

Browse Source 
2001-11-28  Havoc Pennington  <hp@redhat.com>

	* gtk/gtktextview.c (gtk_text_view_paint): put the warning
	explaining the validation error in front of the G_BREAKPOINT

	* gtk/gtkrange.c (gtk_range_adjustment_value_changed): call
	process updates with include_children = FALSE instead of TRUE, so
	we redraw the range only, not the whole darn window.  Making
	GtkRange a NO_WINDOW widget had weirdly caused the text widget
	Trace/breakpoint trap bug to become much easier to trigger.
This commit is contained in:
Havoc Pennington 2001-11-28 20:42:15 +00:00 committed by Havoc Pennington
parent 931fe180ff
commit 53da925c9b
9 changed files with 79 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
ChangeLog
View File

@ -1,3 +1,14 @@
2001-11-28 Havoc Pennington <hp@redhat.com>
* gtk/gtktextview.c (gtk_text_view_paint): put the warning
explaining the validation error in front of the G_BREAKPOINT
* gtk/gtkrange.c (gtk_range_adjustment_value_changed): call
process updates with include_children = FALSE instead of TRUE, so
we redraw the range only, not the whole darn window. Making
GtkRange a NO_WINDOW widget had weirdly caused the text widget
Trace/breakpoint trap bug to become much easier to trigger.
Wed Nov 28 14:12:03 2001 Owen Taylor <otaylor@redhat.com>
* gdk/Makefile.am (gdk_public_h_sources): Remove reference

11
ChangeLog.pre-2-0
View File

@ -1,3 +1,14 @@
2001-11-28 Havoc Pennington <hp@redhat.com>
* gtk/gtktextview.c (gtk_text_view_paint): put the warning
explaining the validation error in front of the G_BREAKPOINT
* gtk/gtkrange.c (gtk_range_adjustment_value_changed): call
process updates with include_children = FALSE instead of TRUE, so
we redraw the range only, not the whole darn window. Making
GtkRange a NO_WINDOW widget had weirdly caused the text widget
Trace/breakpoint trap bug to become much easier to trigger.
Wed Nov 28 14:12:03 2001 Owen Taylor <otaylor@redhat.com>
* gdk/Makefile.am (gdk_public_h_sources): Remove reference

11
ChangeLog.pre-2-10
View File

@ -1,3 +1,14 @@
2001-11-28 Havoc Pennington <hp@redhat.com>
* gtk/gtktextview.c (gtk_text_view_paint): put the warning
explaining the validation error in front of the G_BREAKPOINT
* gtk/gtkrange.c (gtk_range_adjustment_value_changed): call
process updates with include_children = FALSE instead of TRUE, so
we redraw the range only, not the whole darn window. Making
GtkRange a NO_WINDOW widget had weirdly caused the text widget
Trace/breakpoint trap bug to become much easier to trigger.
Wed Nov 28 14:12:03 2001 Owen Taylor <otaylor@redhat.com>
* gdk/Makefile.am (gdk_public_h_sources): Remove reference

11
ChangeLog.pre-2-2
View File

@ -1,3 +1,14 @@
2001-11-28 Havoc Pennington <hp@redhat.com>
* gtk/gtktextview.c (gtk_text_view_paint): put the warning
explaining the validation error in front of the G_BREAKPOINT
* gtk/gtkrange.c (gtk_range_adjustment_value_changed): call
process updates with include_children = FALSE instead of TRUE, so
we redraw the range only, not the whole darn window. Making
GtkRange a NO_WINDOW widget had weirdly caused the text widget
Trace/breakpoint trap bug to become much easier to trigger.
Wed Nov 28 14:12:03 2001 Owen Taylor <otaylor@redhat.com>
* gdk/Makefile.am (gdk_public_h_sources): Remove reference

11
ChangeLog.pre-2-4
View File

@ -1,3 +1,14 @@
2001-11-28 Havoc Pennington <hp@redhat.com>
* gtk/gtktextview.c (gtk_text_view_paint): put the warning
explaining the validation error in front of the G_BREAKPOINT
* gtk/gtkrange.c (gtk_range_adjustment_value_changed): call
process updates with include_children = FALSE instead of TRUE, so
we redraw the range only, not the whole darn window. Making
GtkRange a NO_WINDOW widget had weirdly caused the text widget
Trace/breakpoint trap bug to become much easier to trigger.
Wed Nov 28 14:12:03 2001 Owen Taylor <otaylor@redhat.com>
* gdk/Makefile.am (gdk_public_h_sources): Remove reference

11
ChangeLog.pre-2-6
View File

@ -1,3 +1,14 @@
2001-11-28 Havoc Pennington <hp@redhat.com>
* gtk/gtktextview.c (gtk_text_view_paint): put the warning
explaining the validation error in front of the G_BREAKPOINT
* gtk/gtkrange.c (gtk_range_adjustment_value_changed): call
process updates with include_children = FALSE instead of TRUE, so
we redraw the range only, not the whole darn window. Making
GtkRange a NO_WINDOW widget had weirdly caused the text widget
Trace/breakpoint trap bug to become much easier to trigger.
Wed Nov 28 14:12:03 2001 Owen Taylor <otaylor@redhat.com>
* gdk/Makefile.am (gdk_public_h_sources): Remove reference

11
ChangeLog.pre-2-8
View File

@ -1,3 +1,14 @@
2001-11-28 Havoc Pennington <hp@redhat.com>
* gtk/gtktextview.c (gtk_text_view_paint): put the warning
explaining the validation error in front of the G_BREAKPOINT
* gtk/gtkrange.c (gtk_range_adjustment_value_changed): call
process updates with include_children = FALSE instead of TRUE, so
we redraw the range only, not the whole darn window. Making
GtkRange a NO_WINDOW widget had weirdly caused the text widget
Trace/breakpoint trap bug to become much easier to trigger.
Wed Nov 28 14:12:03 2001 Owen Taylor <otaylor@redhat.com>
* gdk/Makefile.am (gdk_public_h_sources): Remove reference

2
gtk/gtkrange.c
View File

@ -1446,7 +1446,7 @@ gtk_range_adjustment_value_changed (GtkAdjustment *adjustment,
gtk_widget_queue_draw (GTK_WIDGET (range));
/* This is so we don't lag the widget being scrolled. */
if (GTK_WIDGET_REALIZED (range))
gdk_window_process_updates (GTK_WIDGET (range)->window, TRUE);
gdk_window_process_updates (GTK_WIDGET (range)->window, FALSE);
/* Note that we don't round off to range->round_digits here.
* that's because it's really broken to change a value

2
gtk/gtktextview.c
View File

@ -3719,8 +3719,8 @@ gtk_text_view_paint (GtkWidget *widget,
if (!text_view->onscreen_validated)
{
g_warning (G_STRLOC ": somehow some text lines were modified or scrolling occurred since the last validation of lines on the screen - this is a known bug, no need to report.");
G_BREAKPOINT ();
g_warning (G_STRLOC ": somehow some text lines were modified or scrolling occurred since the last validation of lines on the screen");
}
#if 0