[Thomas Leonard - Tue, 21 Jan 2003 05:10:56 AM CST]
> Actually, it might be a PyGTK problem. Looks like the infamous
> ref-counting bug ("this object is only referenced by signal handlers, so
> I'm going to wipe __dict__"):
>
> http://bugzilla.gnome.org/show_bug.cgi?id=92955
I feel silly no
[John Finlay - Wed, 15 Jan 2003 03:03:46 PM CST]
> I'm guessing that your ColorWidgets are somehow losing info because of
> loss of references in python but I don't understand how PyGTK handles
> memory in conjunction with python.
That would definitely cause it
I'm guessing that reference c
[Ava Arachne Jarvis - Wed, 15 Jan 2003 05:25:54 AM CST]
> I'm attaching a version of the program that I stripped down to about 50
> lines. Instruction for running this:
It would help if I attached the program. Heh. Sorry.
--
| BOFH excuse #105:
|
| UPS interrupted the server'
I'm using python 2.2 and pygtk 1.99.14, gtk 2.2.0 and friends.
I'm running across an odd problem when I use a large number of widgets,
and some of them are ones that inherit from original gtk widgets. When
first created, these objects seem intact; however, the first time a
signal callback is cal
