--- In [email protected], "ehathgepiurhe"
<[EMAIL PROTECTED]> wrote:
> --- In [email protected], "brucexs" <[EMAIL PROTECTED]> wrote:
> > Try putting win.debug statements in after each wait to ensure
that
> > your more commands are being executed as expected. What happens?
> >
> > Also try varying the 150 -- what does 1500 do?
> >
> > Before running above with win.debugs, execute win.debug("start")
> just
> > to create debug window.
>
> Hi Bruce,
>
> 1500 and 15000 did the same thing as 150. Will both work fine on
the
> second try, but the first try still does not work. I changed the
> more commands to thus:
> win.debug("start")
> *Wait until activewindow("*SoftCAT*")
> win.debug
> *Wait for (150)
> win.debug
> *Keys {tab}
> win.debug
> *Wait for (150)
> win.debug
> *Keys {tab}
> win.debug
> *Wait for (150)
> win.debug
> *Keys i
> win.debug
> When I started the program, I got a window pop up with 7 blank
> lines, 'start' on the 8th line, and nothing after that.
For the above, it seems the script is running fine. Also, I thought
that maybe the wait until was failing and the script was running
before the program was ready for the keys, but your tests found that
even a with long fixed wait after the wait until, the keys still
don't seem to work.
I see you are tabbing twice and then sending i. I suspect this
means that you are using tab to move the input focus to a different
window. Are you sure the input focus always starts at the same
place?
What happens if you manually type two tabs then i?
Also try
keys {slow}{tab}{tab}i
keys {fast}{tab}{tab}i
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/
