On May 5, 5:21 pm, Carsten Haese <[EMAIL PROTECTED]> wrote: > 'pyuno' objects are proxy objects that represent UNO objects, services, > and interfaces. Since all attribute lookups are handled by the UNO > bridge, the proxy object doesn't actually know what attributes it has, > which is why it won't respond anything useful to the usual dir() > inspection.
I suspected something like that, but couldn't quite believe as CORBA proxies generated by C++/C/Java/Lisp/Python IDL compiler are normal classes which know what methods they have... > To list the methods and properties that the UNO object behind a pyuno > proxy object has, you need to use UNO inspection capabilities. Something > like the following seems to work: Thanks a lot! After reading your example I googled and found unohelper.inspect, which provides all information. But I still need instances, as 'dir(XSingleComponentFactory)' gives just ['__doc__', '__module__', '__pyunointerface__'], and 'unohelper.inspect(XSingleComponentFactory, sys.stdout)' gives segmentation fault. Sincerely yours, Dmitri -- http://mail.python.org/mailman/listinfo/python-list
