--- In [email protected], "Sheri" <sheri...@...> wrote:
> Yes, especially optionals. Optionals are working for the first time. I tested > with "~~", not with typespec. I don't understand what you do for optionals if > there's a typespec. I know you try to allow an optional to be omitted > entirely, and I never thought it should work that way (since most functions > with optionals have multiple optional arguments, and how can you know which > argument belongs to which?) If typspec is "s t s t " That's consistent with a call like anObject.aMethod(astring1, "", astring2, "") or anObject.aMethod(astring1, astring2) The positioning of the "t " optional markers indicates location of parameters to be skipped or ignored. You can skip _all_ parameters corresponding to optional "t " marker, or include them _all_. > > > comPluginDemoScriptTextFromHTMLusingIE.powerpro requires a file named > > > textFromHtml.html (missing from distro) included in COMplugin0.72_100217.zip > > > The script comPluginDemoScriptControlBarOWCchart.powerpro gets this error: Fixed. > > > and got: > > > ERROR: com.get_accessible_object: Alan is an idiot and made a > > > programing error Ditto. > Hmmn. The script comPluginDemoScriptAccessible crashes Powerpro near the end. Can;t replicate. Can you pin down where it's crashing? > Regarding how to signal string arguments without needing the unicode plugin. > Couldn't you replicate the functionality of unicode.new(...) as > com.stringify(...) and recognize this new type of com handle in the same > manner you do a unicode plugin handle? It would be simple to use and we > already know that it works. I'd have to add another kind of handle (returned by com.stringify) which I don't want to add at the moment. Might in future. Your Search (Find?) method: the one that was unhappy with "3333"? What error message do you get with retry on?
