> > So, there is no response regarding PP going crazy, going into an
> > endless loop withut visible reason, and not respecting Cancel
> > command?
> > 1. Whay would this script become "Nested script"
> Maybe the script is called from other script. Anyway, it's safer to
> always use wait.for() unless you have a special reason to use wait
> or wait.until()
No, it is not. It runs, and after the modem is not hung, it waits,
and then jumps back few lines to try to hang up again. I believe
jumping few lines back within the same script should not be "nested".
> > 2. Why does it not respect the Cancel button in a error box
>
> Try the latest build 4.4.04. The handling can be improved.
OK, I will, since this definitively seems like a bug.
> > 3. Why does not PP always sucessfily send a letter Z to the menu
> > which is open?
>
> Does TrayIcon.Right("... z") also have this problem? I assumed
it's a
> timing issue: Keys seems sometimes triggered before the menu is
> activated, so, z goes to the wrong window.
Yes, it had the same problem. Exactly to avoid Keys jumping the gun,
I have first open the menu, then adde bit of wait (now I am on half
a second) and only then I send *Keys z.
currently I am running:
@redial
...
; TrayIcon.Right("SuperDial z") had the same problem
TrayIcon Right SuperDial
wait.for (500)
Keys z
...
if (modem) do
keys {esc}
jump redial
...
I will see in a few days if this new setup helps. Problem is because
this is iregullar, so I can not reporduce the error as I wish, but
must wait until it occures.
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/
<*> 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/
