Created attachment 39532 [details] [review]
Maybe a working patch

I've been playing around with the code to see if I could understand how it
works and I came up with the following patch in the meantime. It seems quite
nice but I don't really know this part of the code and maybe it's totaly wrong.
:)

This patch solves Bug 167379 and Bug 167380 as well.

Oh, I forgot to mention. It's still not possible to copy the Fond and Color
dialogs. Might be the same bug that used to affect the normal dialog?

Created attachment 39589 [details] [review]
Updated patch

I've updated the patch against the latest version from SVN. There are still
some problems though. The widgets can't be loaded from glade files or copied. I
guess there has to be some modifications made to gazpacho/loader/widgettree.py
for this to work?

The proper way of solving this is fixing the bug in pygtk that is blocking us
from creating the widgets with gobject.new.

For the Arrow, we can fix the problem with your patch and also patching
widgetree.py but we still need to do that for every widget that need constructor
parameters. Even worse, we need to call this code whenever we instantiate one of
this widgets (paste, undo delete, ..)

As I said let's fix gobject.new in pygtk first.

I guess this pygtk bug wont be fixed before a 0.5.3 release? If that is the
case, should we remove it as a blocker for Bug 172261? If it isn't fixed for the
next release, maybe we should disable this object in the palette at least.

I'm disabling them from the palette and yes, we should remove them from the
blocking list

Created attachment 47172 [details] [review]
patch against pygtk-2.6.2 that allows gazpacho to create arrows

The attached changes pygtk so that he arguments to gtk.Arrow() are optional.  I
know that this should really be filed against pygtk, but I'm not sure if it
should be attached to Bug #161177 or filed as a separate bug.  Decided to let
someone here work that out.

Fixed this in an alternative way.