|
Re: Using Accessibility interface from PyORBit?: msg#00163gnome.gtk+.python
> Is it possible that you are running into this problem? > http://bugzilla.gnome.org/show_bug.cgi?id=118990 Upgrading to pyorbit from CVS does fix the segfault, but it doesn't fix the problem. I still get a CORBA.NO_IMPLEMENT exception when I try to call registerGlobalEventListener on the Accessibility.Registry. The CORBA exception is raised on line 195 of pyorbit-servant.c, where it has just tried to look up an imethod named "ref" on the servant. The servant implements the Accessible.EventListener interface, and there is no "ref" method declared for that interface. So I'm not surprised it's raising an exception. But why is it trying to find a "ref" method in the first place? Still confused, --Tessa _______________________________________________ pygtk mailing list pygtk@xxxxxxxxxx http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/ |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Embedding a widget in a CellRenderer: 00163, Nicholas Wieland |
|---|---|
| Next by Date: | Re: Conflicting omniORBpy and PyORBit: 00163, Thomas Lockhart |
| Previous by Thread: | Re: Using Accessibility interface from PyORBit?i: 00163, James Henstridge |
| Next by Thread: | Re: Using Accessibility interface from PyORBit?: 00163, James Henstridge |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |