GNOME Bugzilla – Bug 85709
gtk_widget_get_pango_context() and private data
Last modified: 2011-02-04 16:11:17 UTC
gtk_widget_get_pango_context() contains: context = gtk_object_get_data_by_id (GTK_OBJECT (widget), quark_pango_context); if (context) { screen = g_object_get_data (G_OBJECT (context), "gdk-pango-screen"); if (screen && (screen != gtk_widget_get_screen (widget))) context = NULL; } If this is right thing to do, then we need to add gdk_pango_context_get_screen(), since peeking at private object data like this is not allowed. I'm a little concerned about colormap changes and the widget's pango context ... we don't seem to handle this currently. Handling it might automatically have the effect of handling screen changes since a screen change automatically implies a colormap change.
Thu Nov 7 18:50:38 2002 Owen Taylor <otaylor@redhat.com> * gtk/gtkwidget.c (gtk_widget_get_pango_context): Note that get_pango_context() is not "until death does us part", but "until the screen changes". * gtk/gtkwidget.c (gtk_widget_create_pango_context): Add a MULTIHEAD warning. * gtk/gtkwidget.c (do_screen_change): Clear pango context for widget if set. Ignoring colormap problems. Colormap changes after a widget is realized already don't work.