Hi Vic. I remember doing that when I created the wepm but I will go back and modify it to see if it takes. Thanks for the heads up. Rick USA ----- Original Message ----- From: Vic Beckley To: [email protected] Sent: Friday, April 22, 2011 7:04 AM Subject: RE: the notepad2011 app
Rick, In looking at your Notepad2011.wepm file, it looks like you forgot to tell the app to load with Notepad. Do the following: Bring up Package Manager and choose to modify your package. Accept the license. Find the open package file. I had to Alt-Tab to it. Tab to the list of File to Package and arrow down to Notepad2011.vbs. Tab twice to the Associate with Application button and press the spacebar. Now an open dialog will come up. Find and press enter on the Notepad.we file. Once back to Package Manager, you can tab one more time and find what the file is associated with. You will see Notepad.we in the edit box. You may have to arrow down once to see it. Tab to the Create Package and save the package. I hope this helps. I followed the above steps and the app loaded successfully without having to associate it manually. Vic From: RicksPlace [mailto:[email protected]] Sent: Friday, April 22, 2011 5:10 AM To: [email protected] Subject: Re: the notepad2011 app Hi Jeff: I'm sitting here thinking that it is going to be harder to track down buggs on remote systems than on my own machine! i have never had to do this but here goes... I read my code and the script_name is being pulled from the xml file which is assigned the file path via a ClientInformation variable supplied by WindowEyes when the Script is loaded. The code was canned code generated by the WEScriptFramework so should be well tested so I will put that aside temporarily. I did have my script speak the value pulled from the xml file and it was NotePad2011 so that piece of code seems to be working. Let me ask some questions so I can try and define the parameters of the problem: 1) Can you see the NotePad2011 App running in AppManager when you have NotePad open? 2) The warning message is slow to speak - it takes about2 seconds so navigating around faster than that after opening a duplicate NotePad file might step on the warning - something I would need to fixand plan on looking at. Regarding the first question: When I downloaded and Installed the NotePad2011 App I had to go into App Manager and load it manually while NotePad was running. I had to do this even though I think it should have been done automatically when I clicked the Install button. After all Install means install and not just "Place it in a folder". So I am interested in whether others have to do this step when installing scripts. It may be something to dig into deeper. Let me know if either of the 2 above questions seems to relate to the problem or any other ideas or details. Rick USA --- Original Message ----- From: Jeff Weiss To: [email protected] Sent: Friday, April 22, 2011 2:24 AM Subject: the notepad2011 app I think you've done well getting your script package together. When I downloaded the package and attempted to use it, it did not run. Looking at the xml and the vbs files, I think you might add this line near the beginning of the .vbs file: Dim Script_Name : SCRIPT_NAME = "NotePad2011" Initially, this is needed so that your script can identify the file to get your strings. Good job! Keep up the good work. Jeff Weiss
