I didn't say to put it in the loop. I would never clear AT() in a loop. I
said to put it in each case statement.
The only way for the case statement to be entered is by AT() finding the text.
If you don't clear it at that point it will enter the same case statement
repeatedly. You probably don't want it entering the same case statement again
unless that AT() condition is actually satisfied.
As far as the screen moving slower than the script you are absolutely correct.
That is why I always use a stable command before checking for AT()
I don't use rules scripting. I use VB.Net.
--
Bill Palmer
Financial Coordinator, Information Systems
Mid-Columbia Medical Center
The Dalles, OR 97058
541-296-7417
>>> On 3/21/2008 at 2:18 PM, in message <[EMAIL PROTECTED]>,
"Thom C. Blackwell" <[EMAIL PROTECTED]> wrote:
> Greetings,
> Um... I read an "Is Case" as the same thing as an If? ...
>
> Clearing the At - or Rule is a potentially dangerous thing to do and should
> not be done without a really, really, really good reason to do so - here's
> why.
>
> The At / Rule command has built in logic to not allow you to see the same
> thing twice in a row. This is a VERY good thing and is not something to
> override lightly. I've seen countless times where folks put in at"" in a
> loop, and it caused them all sorts of grief tracking down why something
> "odd" happened one day. This is an insidious problem to track down because
> in debug mode it will work perfectly.
>
> Keep in mind that a screen may not move as quickly as a script can - so you
> very well could say:
> Do
> if at("Here") then Enter "Y"
> At""
> Loop until at("There")
>
> And the loop spin so fast that the screen didn't "take" the Y yet and it
> still be at here! Protecting against seeing the same thing twice protects
> you from this - clearing it takes this protection away.
>
> All this stuff is why I like the Rules format especially for conditional
> statements :`)
>
> Regards,
> Thom
>
> Thom C. Blackwell
> Product Manager
> Boston Software Systems
> (866) 653-5105 ex 807
> www.bossoft.com
> Sign up for my weekly webinar!
>
> LEGAL NOTICE Unless expressly stated otherwise, this message is confidential
> and may be privileged. It is intended for the addressee(s) only. Access to
> this E-mail by anyone else is unauthorized. If you are not an addressee, any
> disclosure or copying of the contents of this E-mail or any action taken (or
> not taken) in reliance on it is unauthorized and may be unlawful. If you are
> not an addressee, please inform the sender immediately, then delete this
> message and empty from your trash.
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Bill Palmer
> Sent: Friday, March 21, 2008 4:50 PM
> To: [email protected]
> Subject: RE: [Talk] Using AT() with Select Case
>
> If you decide to go with the Select Case statement be sure to put At("") at
> the end of each Case block. If you don't clear At() it continues to look
> for the same text.
