Cedric Bosdonnat wrote:
Hi everybody,I have developped an UNO component and I found something strange using it in a Basic macro. Let's suppose we have a XFoo interface: <code idl> interface XFoo: com::sun::star::uno::XInterface { [attribute] string Name; }; </code> The component, written in C++ obviously implements the getName() and setName() for this interface. So when using it in basic both calls shoud work:
That you implement an interface attribute with two functions (unfortunately called getAAA and setAAA) in C++ is an "implementation detail" of the C++ UNO language binding. It does not affect how interface attributes are used in other UNO language bindings (and in the Basic UNO lanuage binding, interface attributes are accessed via x = y.AAA and y.AAA = x, as you already mention below).
-Stephan
<code ooobasic> aName = xxx.getName() aName = xxx.Name </code> However, in my case, only the 2nd call works... Does anyone have an idea of the problem ? Thanks for your help, Cedric
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
