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
On May 4, 7:13 pm, Marc 'BlackJack' Rintsch <[EMAIL PROTECTED]> wrote:
> The OPs problem is, there is no access to the class or type because
> there is no name.
Exactly :-(
> You can get just instances from a factory function.
Worse, if I call
localContext.ServiceManage
I'll get something with
On May 5, 1:17 am, Fuzzyman <[EMAIL PROTECTED]> wrote:
> dir(type(localContext))
> Perhaps ?
It gives
['__class__', '__cmp__', '__delattr__', '__doc__', '__getattribute__',
'__hash__', '__init__', '__new__', '__reduce__', '__reduce_ex__',
'__repr__', '__setattr__', '__str__']
while
import sys
di
On 4 май, 09:08, "Gabriel Genellina" <[EMAIL PROTECTED]> wrote:
> En Fri, 04 May 2007 01:34:20 -0300, <[EMAIL PROTECTED]> escribio:
> > I'm not against 'dir(MyClass)'; the question is, what should I 'dir()'
> > to get methods of 'pyuno' type instance?
> Usually instances don't have its own methods,
On May 4, 3:21 am, Stargaming <[EMAIL PROTECTED]> wrote:
> What's wrong about `dir()`?
> x = MyClass()
> x.f()
I want to cashe pointers to Python functions in a non-Python app.
'dir()' requires an argument, and I want to get function pointers
before I have any variable of given type or class.
That
Hello!
If I do
import uno
localContext=uno.getComponentContext()
then localContext is of type
I guess it's a new type provided by PyUNO extension.
localContext.__class__ is None
Is there any way to list all methods of that new type, via Python C
API or through interpreter (other then dir(localC
