David, Your "normally" is exactly how I would code my prompt, that is the proper way to handle what you're describing. I don't know if you also add a Title condition to look for unique text on the screen as well, that is something I try to do with STAR as well. What a prompt rule does is look to see that the words are behind where the cursor, literally reads the screen using left of the current cursor position as a parameter for the View command - so it is dead on at that given beat in time.
At this stage, with the information at hand, all I can do is offer advice. When I have something like this; runs properly most, but not all of the time. When I am being smart and can remember my own advice... I determine the exact sequence of events that would cause failure. E.g.. What would you have had to have done manually to cause the failure. Then, I use that information and meticulously read through my script to see how the script caused every single one of those actions to occur. That approach always works. Vast majority of the time, I find I failed to account for something in how the screens progress - VERY easy to do with STAR btw. Very rarely, I find some genuinely weird application behavior like the system "jitters" the cursor into, out of, and back into that position. Human nature causes us to suspect genuinely weird/magical first. It is very, very hard to resist that urge. And it's impossible to solve problems quickly if you don't! Thom C. Blackwell VP, Technical Services Boston Software Systems, Inc. Phone: 866.653.5105 x807 Mobile: 508.423.8463 Fax: 508.319.3015 www.bostonsoftwaresystems.com <http://www.bostonsoftwaresystems.com/> The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. From: [email protected] [mailto:[email protected]] Sent: Tuesday, June 05, 2012 3:12 PM To: Talk Subject: [talkbws] McKWEM Prompts vs. cursor location I have a rules based script connecting to McKWEM that very intermittently gets out of sync with the host app screen. I'm wondering if it has to do with the way the prompts were coded. For example, to match the prompt below, I'd normally just look for the first few words at the beginning of the line i.e. "Enter range of pages". What is the recommended way to code for the prompt below to ensure the system is ready to accept input? In this example, the cursor is not always going to land in the same location because the number of pages is variable. Enter range of pages to print (i.e. 4-7, 8) (max 21)-- ΒΆ Thanks! David Garcia Senior Programmer/Analyst Washington Hospital Healthcare System 2000 Mowry Avenue Fremont, CA 94538 (510) 745-6477 || (510) 797-1111 x4760 (408) 340-0209 (cell) [email protected] <mailto:[email protected]> --- To post a message to this list, send mail to: [email protected] You are currently subscribed as: [email protected] Unsubscribe in the customer center on our website: http://www.bostonworkstation.com/customer_center/virtual_user_group_talk.aspx --- To post a message to this list, send mail to: [email protected] You are currently subscribed as: [email protected] Unsubscribe in the customer center on our website: http://www.bostonworkstation.com/customer_center/virtual_user_group_talk.aspx
