Greetings, Ah yes - "the old popups that have nothing to do at all with the currently scripted application problem".
With Windows connection scripts in general the WorkStation is going to "force focus" to the application it's talking automatically. If the window is something that is associated with the application, then it will be the "thing" that has focus as far as BWS is concerned and you can have a rule that evaluates for its existence. If the window is not associated with the application, and it forces you to close it before anything else can be done on the PC, then something will need to detect it and close it. This is a scenario that can happen with Web connection scripts btw - the browser popping up windows that are not HTLM - therefore the Web connection can't see them since it only understands HTML pages in a browser. There is an example project on the website that handles these situations - and can be used to handle what you're describing as well - it's under the Web Connection section called WindowWatcher. Give Support a ring for more info on its use - where I've used it before it really works great for handling these sorts of situations. Regards, Thom Thom C. Blackwell Product Manager Boston Software Systems www.BostonWorkStation.com 866 653-5105 - ex 807 [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Hans Sent: Monday, May 08, 2006 10:33 AM To: [email protected] Subject: [Talk] How do I handle a window(s) that open while a BWS script is running? Hello, While my BWS script is running, a window may open stating some sort of error (e.g. Disk or Network error). The window may be issued by the application BWS is interacting with or it may be from the Windows OS. How do I handle these events? Can I do a check or a rule to ensure that the app BWS is working with has focus or is active? Thanks, Neil Hans Alegent Health Omaha, NE
