To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=53818
------- Additional comments from [EMAIL PROTECTED] Wed Aug 31 06:38:19 -0700 2005 ------- Andreas, leaving the issue of declaring an object as an uno type aside ( I think this is a result of my badly formed example confusing the issue I want to highlight ) for the previous example you could write obj1 = createUnoService( "myModule.XSomething" ) obj2 = createUnoService( "myModule.XSomething" ) instead. The issue is that when basic encounters a [ sequence< sequence < Any > > ] wrapped in an Any ( e.g. obtained from an UNO component ) and later tries to pass that object to another (or even the same ) UNO object it will change the type of that object from [ sequence< sequence < Any > > ] to [ sequence< sequence < something > > ] where something is the type of value contained in the Any. I presume this is a result of some sort of best fit algo in the basic runtime but... you would know better about that :-) So does that clarify the problem or have I confused things more? Note in the "confusing" example written earlier the basic statement "obj1.Value = obj2.Value" equates to obj1.setValue( obj2.getValue ), Value is an idl attribute, hth --------------------------------------------------------------------- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
