--- In [email protected], "entropyreduction"
<alancampbelllists+ya...@...> wrote:
>
> --- In [email protected], "Sheri" <sherip99@> wrote:
> >
> >
> > In my textframe contents test script, I made these changes:
> >
> > win.debug("unicode.version",unicode.version) ;;debugs 0075
> > com.return_unicode_strings(1)
> > unicode.messagebox("OK", appref.Selection.Item(1).contents)
> >
> > and the contents appears on the "unicode" messagebox in ANSI.
> > There were question marks substituted for high characters just as
> > previously appeared on debug.
can now get_object_description for the created Application object. But can no
longer do much of anything else due to optional variable problem "Type
Mismatch" errors. E.g., leaving off unicode for now:
win.debug(appref.Selection.Item(1).contents)
produces
ERROR: com.method: Optional variable type problem (sys code 80020005: "Type
mismatch.")
If I click ok, new error message says:
Invalid use of period: cannot load plugin, invalid handle value, or invalid
function.
You mentioned elsewhere the documenter.vbs script which I too had used on the
TLB file. It does not show the methods, etc., for subobjects. With the "old"
implementation of get_object_description("f") I was able to see the methods and
properties (sans types) for a TextFrame when fed appRef.Selection.Item(1)
[assuming a text frame was the sole selection in the application.] I'm certain
I was able to see that appRef.Selection.Item(1) was a "TextFrame" when I used
one of the other options of get_object_description.
Regards,
Sheri
