--- In [email protected], "Sheri" <[EMAIL PROTECTED]> wrote:
>
> Would it be possible to add scripting support for various options?
>
> Current problem is, I would like my script to know whether the
> configuration's default is currently to use fast key sends (or
not)
> and be able to change it on request.
I am not sure why you need this. If you find some keys that depend
on the method of sending, just add {slow}, {fast} to the front.
>
> Its not currently permitted to have {fast} for one part of a
> keystring and {slow} for another (makes use of the filemenu
approach
> not very useful for me). I need {fast} or the shift key isn't
> recognized, but {slow} if a keystring causes dialogs to be
launched
> where subsequent keys need to be targetting the dialog instead of
> the initial window. It also is not not currently permitted to have
> multiple {to xxx} in a single keystring.
>
> Any chance to allow a single keystring to support multiple {to
xxx},
> {fast} and {slow} tokens?
No, sorry, this would be a fairly substantial internal design change.
And it would end up doing exactly the same as specifying multiple
keys statements, each one starting with {slow} or {fast} BTW,
latest beta and possibly 4.5 also support a third option {sinp},
which you may want to try.
I would not trust the help on which methods work with which keys (in
fact I have removed that material from latest versions). I would
just experiment. On my machine, {slow} works fine with all normal
shifted keys, that is
keys [EMAIL PROTECTED]&*()_{+}{{}}|
keys {slow}{enter}+`+1+2+3+4+5+6+7+8+9+0+-+=[+]+\
keys {slow}{enter}{shift}`1234567890-=[]\{shift}
keys {slow}{enter}ZAQXC<>?:"
keys {slow}{enter}+z+a+q+x+c+,+.+/+;+'
keys {slow}{enter}{shift}zaqxc,./;'{shift}
All three versions of the keys statements produce the same results.
(The first line has to use {x} for the special keys + % ^.)
Make sure you use +x or {shift}x{shift} for shifting. The + form is
possibly more reliable.
If you do find you have to have mixed key sending types in one line
that you read from filemenu function, you can just parse that line
with regular expressions (or index function and select) and generate
multiple win.keys statements.
Also, AFAIK, both slow and fast handle multiple windows. You may
need to put waits {wn} between or even split to multiple key
statements with longer waits in between (but I think you can
multiple {wn} in a row too).
Attention: PowerPro's Web site has moved: http://www.ppro.org
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/power-pro/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/power-pro/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
