Tabbed version of Dillo, remarks
One last thing before I go to sleep... As already stated in the documentation (doc/DilloDoc.txt, but who reads documentation anyway?), the tabbed version of Dillo sometimes (to be specific, when loading a tab in the background) produces Gdk_CRITICAL messages on stderr. Like these: Gdk-CRITICAL **: file gdkwindow.c: line 1274 (gdk_window_set_cursor): assertion `window != NULL' failed. These messages come from deep within dw_widget (line 706), and seem to be caused by an error/a bug in the widget. What seems to happen is that the widget tries to reset the cursor for a non-existing window (gdk_window_set_cursor (GTK_LAYOUT(viewport)->bin_window, NULL while the viewport does not yes have a bin_window defined). Sebastian, any input on this? Cheers//Frank -- WWWWW ________________________ ## o o\ / Frank de Lange \ }# \| / +46-734352015 \ \ `--| _/ <Hacker for Hire> \ `---' \ +31-640037120 / \ frank@unternet.org / `------------------------' [ "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." ]
On Tue, Jun 17, Frank de Lange wrote:
One last thing before I go to sleep...
As already stated in the documentation (doc/DilloDoc.txt, but who reads documentation anyway?), the tabbed version of Dillo sometimes (to be specific, when loading a tab in the background) produces Gdk_CRITICAL messages on stderr. Like these:
Gdk-CRITICAL **: file gdkwindow.c: line 1274 (gdk_window_set_cursor): assertion `window != NULL' failed.
These messages come from deep within dw_widget (line 706), and seem to be caused by an error/a bug in the widget. What seems to happen is that the widget tries to reset the cursor for a non-existing window (gdk_window_set_cursor (GTK_LAYOUT(viewport)->bin_window, NULL while the viewport does not yes have a bin_window defined).
Sebastian, any input on this?
The only thing I can guess now is that the viewport has not been realized now, which is necessary before a DwWidget is added. You may have to enforce this explicitly by gtk_widget_realize. BTW, you can call any Gtk+ program with the "--g-fatal-warnings" option, this will cause the program to abort, so you can get a backtrace in gdb. Sebastian
participants (2)
-
Frank de Lange
-
Sebastian Geerken