On 12.07.2010 09:14, Stephan Bergmann wrote:
> Yes, it is most likely the specific UNO object implementation that
> causes the problems you describe, not the UNO infrastructure.  You
> need to look up the implementation of that EllipsesShape to find out.
Thank you for clarifying, Stephan. Will file an issue (also
RectangleShape seems to behave like EllipsesShape).

---rony

>
> On 07/11/10 16:24, Rony G. Flatscher wrote:
>> Hi there,
>>
>> just stumbled over the
>> "http://api.openoffice.org/docs/common/ref/com/sun/star/drawing/ConnectorShape";
>>
>> service, which has two UNO long (i.e. java.lang.Integer) properties,
>> named "StartGluePointIndex" and "EndGluePointIndex". Here exceptions get
>> thrown, if one supplies a String object (with the numbers, "2" and "4").
>> Could it therfore be, that "EllipsesShape" is at fault?
>>
>> ---rony
>>
>>
>>
>> On 11.07.2010 15:49, Rony G. Flatscher wrote:
>>> Hi there,
>>>
>>> while tidying up some nutshells, I ran into the following problem:
>>>
>>>      * setting a PropertyValue to a value with a wrong data type will
>>>        correctly cause an exception;
>>>            o the Java exception handler will look up the correct
>>> property
>>>              data type and will then set the property to the new value
>>>              using the correct datatype (which fine).
>>>      * however, setting the two properties "CircleStartAngle" and
>>>        "CircleEndAngle" via Java supplying a String object
>>> containing all
>>>        decimal numbers, does not throw an exception, therefore the
>>>        exception handler does not get triggered and is not able to
>>> render
>>>        the value to the correct type (in this case to a type of
>>>        java.lang.Integer)!
>>>        The old value remains unchanged, if a string value is supplied!
>>>
>>> The used infrastructure (Java based) is dependent on receiving an
>>> exception, if the wrong datatype was assumed (defaulting to a String
>>> object value). The properties in question are "CircleStartAngle" and
>>> "CircleEndAngle" which both are defined to be of UNO type "long" (cf.
>>> <http://api.openoffice.org/docs/common/ref/com/sun/star/drawing/EllipseShape>).
>>>
>>>
>>>
>>> Any ideas what might cause this rather strange behaviour?
>>>
>>> ---rony
>>>
>>> P.S.: Setting the mentioned property values explicitly as
>>> java.lang.Integer values works as expected.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org
For additional commands, e-mail: dev-h...@api.openoffice.org

Reply via email to