We have two models for scripting the "Simple" format (like Key, Pause) and the "Object" format (like R.Key, R.Pause). The Simple format is essentially the same as Object format that it's wrapped around the code in the Tools module which hides the "R."'s and does other things like inserts DoEvents and feeds the Note and Status boxes. We use VB's error handlers to create events in Boston WorkStation's core dll that are caught in the VB code to run DoEvents and Sleeps that reduce a script's activity while it's waiting for a application to present a screen or accept a key.
By going to the object format, the updating of the Status box is circumvented until after we stuff something else in over it, thereby hiding the password. Is this better or worse? Rich McNeil Boston Software Systems 866 653 5105 www.bostonworkstation.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, May 17, 2004 1:39 PM To: [EMAIL PROTECTED] Subject: RE: [Talk] Controlling what prints in the Status box The code below does work, but I don't understand why. Can you explain? I'd like to understand it better. I understand the On Error syntax in general, but why should these two statements do anything in the positions they are in below, where the statements that follow them don't see to be anything that would cause an error? Are they forcing the internal working of the code to move on immediately after the Enter statements in order to assess the result of the Enter? Is that what happens? Henry Taylor Technical Analyst II Lutheran Health Network Ph. (260) 425-3914 |--------+--------------------------------> | | "Rich McNeil" | | | <[EMAIL PROTECTED]> | | | Sent by: | | | [EMAIL PROTECTED]| | | TATION.COM | | | | | | | | | 05/17/2004 10:27 AM | | | Please respond to Talk| | | | |--------+--------------------------------> >--------------------------------------------------------------------------- --------------------------------| | | | To: <[EMAIL PROTECTED]> | | cc: | | Subject: RE: [Talk] Controlling what prints in the Status box | >--------------------------------------------------------------------------- --------------------------------| Boston WorkStation updates its Status box in a slow and occasional way, so the trick here is to introduce another status before the "Keying password" Status can get in. In the VBA in version 6.5 I used the following script with the demo1 application: On Error Resume Next 'makes sure I don't hang around the Enter too long R.Enter "1001" 'I want to hide this. Note I'm directly accessing the WinScript object R On Error Goto 0 R.Status = "Hide Password" 'Overwrites the Status Rich McNeil Boston Software Systems 866 653 5105 www.bostonworkstation.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, May 17, 2004 10:35 AM To: [EMAIL PROTECTED] Subject: [Talk] Controlling what prints in the Status box Is there a way to do this? I'd like to keep the Status box displayed on the BWS window, but it has the bad characteristic of showing the password that's being typed. Can I selectively change or suppress what prints in the Status box? Henry Taylor Technical Analyst II Lutheran Health Network Ph. (260) 425-3914
