On Fri, 2005-04-08 at 10:48 -0300, Johan Dahlin wrote: > >>I put these in because they came from gda_init() which is never called in > >>the python module. Note that I did had set GETTEXT_PACKAGE to libgda-2, > >>too. The idea obviously was that libgda warnings or errors be localized. > >> > >> > The best approach here is to call gda_init() in your module init > function and then let the library worry about the rest. It's usually a > bad idea to copy code from a library into a wrapper.
Thanks. I've done that, by looking at the pygtk/gtk/gtkmodule.c:gtkinit () code. > >Yes, I regenerated the defs file, and added your BoxedTypes definitions > >to it. I don't know what's normal, but I guessed that h2defs.py would > >create correct .defs, and it seems to work. > > > > > h2defs.py is not perfect, it happens from time to time that it does not > pick up stuff from headers properly, especially if you're not using the > gtk+ coding style. OK. Now I understand that the "method" is not meant to be the C function name, but should be the name of the method inside the object, or a global function inside the module. I have rename the gda_config_* methods to config_* in the .defs file, like it was in pygda 0.3.0. However, isn't this possible in python/pygtk? gda.Config.get_key(). instead of gda.config_get_key(). even if there is no GdaConfig object? -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
