--- In [email protected], "entropyreduction" <alancampbelllists+ya...@...> wrote: > > --- In [email protected], "Sheri" <sherip99@> wrote: > > > > > comPlugin0.72_100211.zip > > > > > > I think fixes above problem. Also have another check on optionals... > > > > Yes! I think you did it. > > Optionals as well?
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?) > > > comPluginDemoScriptTextFromHTMLusingIE.powerpro requires a file named > > textFromHtml.html (missing from distro) > > > > The script comPluginDemoScriptControlBarOWCchart.powerpro gets this error: > > ......<snip>...... > > Thanks will fix both. > > > and got: > > ERROR: com.get_accessible_object: Alan is an idiot and made a > > programing error > > To the point.... > Hmmn. The script comPluginDemoScriptAccessible crashes Powerpro near the end. 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. Regards, Sheri
