[pygtk] pygtk documentation

2003-03-09 Thread Padraig
Hi, some comments regarding the pygtk documentation. I found codegen/docgen.py which produces docbook and I think you used http://docbook.sourceforge.net/projects/xsl/ to generate: http://www.gnome.org/~james/pygtk-docs/ This URL is very useful to me, though I was unable to build the documentation

Re: [pygtk] libglade, python and gnome widgets: segmentation fault

2002-10-30 Thread Padraig Brady
Christian Reis wrote: On Wed, Oct 30, 2002 at 05:18:51PM +, Padraig Brady wrote: Where can I get a pygnome corresponding to gtk-0.6.11 ? It's gnome-python cheers Anyway I broke by dependencies (--nodeps --force) just for you :-) And still same error. I created a button with

Re: [pygtk] libglade, python and gnome widgets: segmentation fault

2002-10-30 Thread Padraig Brady
Padraig Brady wrote: Christian Reis wrote: On Wed, Oct 30, 2002 at 03:14:38PM +, Padraig Brady wrote: Thanks for the info, I've noticed that (with pygtk-0.6.8-3) if you use any gnome stuff (even non obvious stuff like stock icons for buttons), then it will crash unless you import gno

Re: [pygtk] libglade, python and gnome widgets: segmentation fault

2002-10-30 Thread Padraig Brady
Christian Reis wrote: On Wed, Oct 30, 2002 at 03:14:38PM +, Padraig Brady wrote: Thanks for the info, I've noticed that (with pygtk-0.6.8-3) if you use any gnome stuff (even non obvious stuff like stock icons for buttons), then it will crash unless you import gnome.ui Can you test

Re: [pygtk] libglade, python and gnome widgets: segmentation fault

2002-10-30 Thread Padraig Brady
Christian Reis wrote: On Wed, Oct 23, 2002 at 01:33:25PM +0100, Padraig Brady wrote: > > GnomeUI-CRITICAL **: file gnome-app.c: line 208 (gnome_app_new): assertion `appname != NULL' failed. > > Gtk-WARNING **: invalid cast from (NULL) pointer to `GnomeApp' > zsh: s

[pygtk] libglade, python and gnome widgets: segmentation fault

2002-10-30 Thread Padraig Brady
Juri wrote: > Hi, > > I was going to ask about how to get Gnome widgets to work with > libglade and python but apparently I solved the problem. I've seen > other people complaining about the problem but no solution, so I > decided to post this anyway; consider it a bug report. I was getting > this