Possible bug: gtk_tree_item_remove_subtree()
- From: <adustman comstar net>
- To: gtk-list redhat com
- Subject: Possible bug: gtk_tree_item_remove_subtree()
- Date: Mon, 20 Apr 1998 14:21:12 -0400 (EDT)
I am, by far, no expert on GTK, but I suspect I have found a bug in
gtk_tree_item_remove_subtree(). All my practical experience with GTK is
through the Python interface, but I do find myself reading the sources a
lot to figure out what's going on.
I am working on an app with dynamic trees, i.e., the nodes are created and
destroyed as needed. When I try to remove the subtree, I get:
** WARNING **: file gtkcontainer.c: line 350 (gtk_container_remove):
"widget->parent == GTK_WIDGET (container)"
** WARNING **: file gtkcontainer.c: line 337 (gtk_container_add):
"widget->parent == NULL"
** ERROR **: sigsegv caught
A quick inspection of gtktreeitem.c:1010-1016 reveals:
if (item->pixmaps_box)
{
gtk_container_remove (GTK_CONTAINER (item->pixmaps_box),
item->minus_pix_widget);
gtk_container_add (GTK_CONTAINER (item->pixmaps_box),
item->plus_pix_widget);
}
I thought of checking for some existing demo code to check against. As it
turns out, nothing that I can find calls gtk_tree_item_remove_subtree(),
and I have checked all the GTK examples, testgtk, and the GIMP source
tree. I'm modeling of pygtk's browse.py example, and it crashes the same
way. (I've already posted this problem to the pygtk list.)
Environment: RedHat 5.0, Linux-2.1.97, GTK+-1.0.0, pygtyk-0.4.1. (And if I
had a backtrace, I would post it...)
--
Andy Dustman Charles Babbage:
ComStar Communications Corp. He never used Linux,
(770) 333-8779 | PGP KeyID=0xC72F3F1D and now, he's dead.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]