--- In [email protected], "Sheri" <sheri...@...> wrote:
> 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.
Which suggests that something that's supposed to be coughing up a handle,
isn't. The only method call that's (a) supposed to return a handle and (b)
take's arguments, seems to be
appref.Selection.Item(1)
So does
h = appref.Selection.Item(1)
generate type mismatch error?
If so, I need results from
h = appref.Selection
h.get_object_description("fn")
(not all of it, just tell me type of parameter supplied to Item; or use your
favour type analyser to get same info).
You get the drill: I can;t reproduce, so you have to tell me
what's going on.
If you have time to run any sample scripts in 0.72 distro, do, tell me if they
generate similar errors.
> 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.
n for name, d for description, f for function
see 12.6 get_object_description in rtf in COMplugin0.72.zip
