Joerg Budischewski wrote:
Hi,
I think, you need to distinguish between different concepts.
a) Properties defined at a service
b) Attributes defined at an interface
c) Methods with
<type> getXXX()
void setXXX( <type> )
defined at an interface (and the get/set function do not throw an
exception except a RuntimeException).
From basic (and python and e.g. OLE automation script languages), a) +
b) + c) can be accessed with o.XXX, but only c) can be accessed with
o.setXXX().
And just for the records, a) is also accessible with o.getPropertyValue(
"XXX"), while b) and c) is in general not accessible via this method.
Bye,
Joerg
Thanks Jörg for explaining this. Until last night, I was not aware of
the special handling for (c), so now I can better understand the
confusion of Cedric and Laurent.
By the way, I assume that, strictly speaking, (a) does not encompass
properties statically defined at a service, but rather properties
dynamically available via XPropertySet at an object (where it would of
course be a violation of service specification if the former was not a
subset of the latter, modulo optional properties). Probably Andreas
Bregas can shed some further light on this.
-Stephan
Laurent Godard wrote:
Hi stephan
3 UNO Basic language binding:
n = o.A;
Only within 2 (the UNO C++ language binding) does the notion of
"getA" exist---that is why I earlier wrote that it is an
"implementation detail" of the UNO C++ language binding.
why do we have in numerous cases in OOoBasic
n=o.A
and
n = o.getA
n = o.setA
eg.
myDoc.Text and myDoc.getText() returning the same object
a lot of roperties are like that !! a lot
Laurent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
