RE: [Talk] My first pathetic attempt with NUI

[thomb]

Greetings, Yikes – I can’t believe I missed this! Connect "C:\Program Files\MEDITECH\Workstation4.x\t.exe", stStream Is all wrong – this should read: Connect "MeditechNUI", stStream   So the start of your script should read: ShellCheck = Shell("c:\bss70\meditechnuiserver.exe", 4) Connect "MeditechNUI", stStream   Give that a go and things should work much better!   As an aside…I’m not familiar with the ShellCheck = Shell("c:\bss70\meditechnuiserver.exe", 4) – I am assuming it launched the NUI Server…   I typically use a BWS shell command:   Shell_ """C:\Bss70\MeditechNUIServer.exe"""   And, Key "@_MINIMIZE" Will minimize the MeditechNUI Server if you don’t want if “visible”.   Sorry for not catching this earlier (of course what I sent will be good advice once you get to the dialog boxes).   Regards, Thom C. Blackwell       From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Shirley Hammack Sent: Friday, April 29, 2005 6:23 PM To: Talk@BOSTONWORKSTATION.COM Subject: RE: [Talk] My first pathetic attempt with NUI   Hey Thom,   When I first used the "learn" process the pause strings were showing in the window of the BWS main screen, but later they didn't show.  When run the script the MeditechNUIServer has focus.  I don't think this is a dialog box because it certainly doesn't accept any kind of keystrokes.  If I close this box manually the Meditech Workstation 4 also closes.  Is there a command to simply put the focus back on the Meditech window?   More questions later, Shirley Hammack IS Financial Analyst Jackson County Memorial Hospital 580-482-4781 ext 2554 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of thomb Sent: Friday, April 29, 2005 4:14 PM To: Talk@BOSTONWORKSTATION.COM Subject: [Talk] My first pathetic attempt with NUI Greetings, Ha ha ha! - just kidding – the script looked fine to me. The biggest difference between NUI and Remote WorkStation 3.x is interacting with the "windows like" dialog boxes that appear when you hit F12 or hit an error etc. You typically just need to send one key to clear these – like a Y or and O or Enter. To send keystrokes to those you use: Key "@_DIALOG:xxx" Where xxx is the key you want to send – so for example, if you need to send a Y the command would be key “@_DIALOG:Y” to “learn” this from the WorkStation, you’d type in: @_DIALOG:Y in the data window and use the Key command. To send an enter you’d use: Key “@_DIALOG:{ENTER}”   Also, I noticed you’d commented out your pauses – not sure why? They looked like valid pauses to me. I’m guessing you got hung up on one of these dialog windows at the end of the script, thought that something was wrong etc. Take the comments off, and remove the stables and use @_DIALOG: if you’re seen a “prompt”.   One final note, and this may be a WebEx related issue, but I have seen when you send the @_DIALOG from the WorkStation (when you are recording a script – not when its running) that when you build the Key command, it switches over to Meditech but the key doesn’t “go through”. The command will work fine in runtime, just something you might see on a slower machine, or when doing remote development.   Let me know if the above does not help. Regards, Thom     Thom C. Blackwell Product Manager Boston Software Systems www.BostonWorkStation.com 866 653-5105 - ex 5 [EMAIL PROTECTED]   This email has been scanned by the JCMH McAfee Webshield appliance and has been cleared for delivery. If you have any concerns or questions, call the IT Helpdesk at x2646. The documents accompanying this transmission contain confidential information, belonging to the sender, that is legally privileged. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information after its stated need has been fulfilled. If you are not the intended recipient, you are hereby notified that any reading, disclosure, copying, distribution, or action taken in reliance on the contents of these documents is strictly prohibited. Violators may be prosecuted. If you have received this email in error, please notify the sender immediately and destroy the transmitted information.