To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116184
User ab changed the following:
What |Old value |New value
================================================================================
Assigned to|ab |tbo
--------------------------------------------------------------------------------
------- Additional comments from a...@openoffice.org Thu Jan 6 16:47:23 +0000
2011 -------
ab->tbo: Please verify using my test document
Now there are four ways to represent a UNO type in Basic:
In case the API expects an any of type "type" CreateUnoValue
has to be used. First parameter has to be "type", second pa-
rameter has to be the XIdlClass corresponding to the type
(e.g. returned by calls to the CoreReflection service, see
test document) or the UNO type name:
MyUnoObj.MethodWithTypeAnyParameter( CreateUnoValue( "type", <XIdlClass as
Object> ) )
or
MyUnoObj.MethodWithTypeAnyParameter( CreateUnoValue( "type", <UNO type name as
string> ) )
In case the API expects a type directly, CreateUnoValue is
obsole, XIdlClass or the UNO type name can be used directly:
MyUnoObj.MethodWithTypeParameter( <XIdlClass as Object> )
or
MyUnoObj.MethodWithTypeAnyParameter( <UNO type name as string> )
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@api.openoffice.org
For additional commands, e-mail: issues-h...@api.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
