--- In [email protected], "Sheri" <sheri...@...> wrote: > > --- In [email protected], "entropyreduction" > <alancampbelllists+yahoo@> wrote: > > > So, I can determine the type of every parameter from ITypeInfo > > (got it here: http://spec.winprog.org/typeinf2/) > Enjoyably written, though beyond my comprehension.
Yeah, he writes well. There are three installments of it. > > So, all the _type services are now unnecessary. > > Stay tuned, will take a while to sort out, among other things > > what to do with trailing VARIANT parameters. > Could what you allow as BSTR (for unicode purposes) actually be VARIANT in > this app? All arguments when invoking a com method/get/put are VARIANTs. They are just different flavours of VARIANT. Each VARIANT has a vt member, which may be e.g. VT_BSTR. > Do you think it could be of any use to look at the TLB (even though you can't > create the objects)? > > I have an old version of the app and TLB. Brother Gabriel-Marie sent me the > newer version's TLB and I was at least able to see it with Word's VBA Object > Browser, so you might be able to do something with my version's. Have posted > TLB.zip in your temp files folder. The method I am using to test unicode is > Textframe's Search method. Unicode-handle arguments for either or both > parameter strings did work in the com 72 plugin dated 11/25, but not with any > com plugin test version since. OKay, got the tlb, will look at it later. Posted up comPlugin0.72_091203.zip in http://tech.groups.yahoo.com/group/power-pro/files/0_TEMP_/AlansPluginProvisional/ which fixes problems with put service calls. It includes comPluginDemoScriptSAPI.powerpro which uses com.get_object_description. Work or not for you? (assuming you have SAPI installed). BTW what happens when you call appref.get_object_description (without any argument)?
