http://openoffice.org/bugzilla/show_bug.cgi?id=117382
Issue Type: DEFECT
Summary: calling automation objects from OOo fails
Classification: Code
Product: framework
Version: DEV300m101
Platform: PC
OS/Version: Windows 2000
Status: NEW
Priority: P3
Component: code
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected]
...because of insufficient type information provided by the automation object.
This happens if the automation object has function which take VARIANTS as
arguments but expect a particular type within them. The type information will
then only provide the information, that a VARIANT is expected. So, if a
function is called from OOo Basic, then the bridge will try to convert the UNO
type to the appropriate automation type using a defined mapping (provided that
the target type is a VARIANT). If the uno type is a long (4byte) then it will
be converted to a VT_I4 type. If the implementation of the function expects a
short, then the function may fail.
Similarly the default mapping of UNO Sequences is SAFEARRAY containing
Variants. This is because automation languages, for example VBScript, JScript,
cannot deal with SAFEARRAYs of a particular type.
--
Configure bugmail: http://openoffice.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification
from Bugzilla. Please log into the website and enter your comments.
---------------------------------------------------------------------
--
-----------------------------------------------------------------
To unsubscribe send email to [email protected]
For additional commands send email to [email protected]
with Subject: help
--
-----------------------------------------------------------------
To unsubscribe send email to [email protected]
For additional commands send email to [email protected]
with Subject: help
