--- In [email protected], "Sheri" <sheri...@...> wrote:
>
> Oops, sorry some of my issues were due to having error display turned off. I
> wasn't seeing the count mismatch error when setting IgnoreCaps parameter.
> That is a problem that might could be avoided if a count mismatch caused the
> typespec to be ignored for that invoke.
>
> But there is still a problem with skipped params.
>
> Use following corrected version.
I'll go over it in the next few days.
Meanwhile:
AppRef.CheckSpelling, second parameter, is a good example of a parameter than
no guessing could ever get right. Excel VBA docs
"CustomDictionary: Optional Variant. A string that indicates the file name of
the custom dictionary to be examined if the word isn't found in the main
dictionary. If this argument is omitted, the currently specified dictionary is
used."
So have to use a type_spec to omit. In VBA you'd use named arguments if you
wanted to omit CustomDictionary:
AppRef.CheckSpelling(Word:=HAX, IgnoreUppercase:=1)
which would be a nice way to do things in powerpro but ugly to implement
without a complicated change by Bruce.
======
Meanwhile, I asked in previous post:
instead of using typespec for omitted optionals:
Have configi ini key SkippedArgument=~~ (or whatever)
Overridden by com.setSkippedArgument("~~")(or whatever)
"~~" (or whatever) only of course valid for parameter known to be optional
Any suggestions for very unlikely string never gonna be legal as a genuine
optional argument value? Could I suppose be character outside norma ansi range
e.g. \xFE
Reaction?
======
> exec.onerror("display")
> global com_status, com_type
....(snip)...
