Hi Chip: Thanks, I was wondering about that. Do you want the WalkThrough that goes along with the NotePad App? It includes a modified version of the first walkthrough, the addition of Norwegian Language support, creating a AppCentral account, a AppManager Package and uploading to App Central and a way to test the Upload. Rick USA ---- Original Message ----- From: Chip Orange To: [email protected] Sent: Monday, April 25, 2011 7:57 PM Subject: RE: NotePad2011 seems to be good now
Hi Rick, not Vic obviously, but yes, when you have an associated app with a program, and you have more than one instance of the program running, then you'll have more than one instance of the app running as well. I should have thought of this when I knew you were going to make this into an associated app, it just slipped by me. making it global, for this reason and the one you proposed, to find other apps which also allow you to open multiple copies of the same file, seems the best solution. I'm not sure however, if you make an upgraded version be global, if it will remove the association or not. We did find unfortunately that upgrading an app didn't remove previous versions under different names, so it appears that an uninstall does not happen when an upgrade occurs. so, you may want to experiment on yourself, and if you find the association is still present in the notepad.we file, well, I can show you how to remove it yourself, since a .we file is just a .ini file, and the WE object model provides you with tools for modifying an .ini file easily. good luck, Chip ------------------------------------------------------------------------------ From: RicksPlace [mailto:[email protected]] Sent: Monday, April 25, 2011 9:53 AM To: [email protected] Subject: Re: NotePad2011 seems to be good now Hi Vic: Are you saying that each time another new instance of a NotePad file is opened a new instance of the Associated NotePad2011 script is also loaded? Right now I am working on thinking of converting it to a global script and perhaps checking for other editor duplicates like VBSedit, WordPad Jamal's Editor, I forget what it's called and any others that might allow for scripting based on their opening Child Window. I am currently creating a little analysis tool to check details of any opened children of the desktop that are MDI or Overlapped. Rick USA ----- Original Message ----- From: Vic Beckley To: [email protected] Sent: Monday, April 25, 2011 7:11 AM Subject: RE: NotePad2011 seems to be good now Chip and Rick, Since all the app does is check for duplicate filenames on the start of Notepad, couldn't you use the StopScript method of the Script object to stop the app once it is finished with its filename processing? This would avoid having multiple copies of the app running at the same time, but it would run again and do its file checking on the launch of another Notepad window. Vic From: Chip Orange [mailto:[email protected]] Sent: Sunday, April 24, 2011 8:11 PM To: [email protected] Subject: RE: NotePad2011 seems to be good now probably best just to leave that to the user; they may have a reason for opening a second copy. actually, just opening the same file name stored in a different directory will generate a warning message, and this may be a legitimate thing to do. Chip ---------------------------------------------------------------------------- From: RicksPlace [mailto:[email protected]] Sent: Sunday, April 24, 2011 4:24 PM To: [email protected] Subject: Re: NotePad2011 seems to be good now Hi Jeff: I will make a note of that for my planned update. I am also thinking of popping up a message box and asking if the user really wants the new duplicate instance opened. One question I will need to research and haven't seen anything on in my readings is how to terminate a process or just close the opened instance of NotePad if the user does not want the new instance opened. I think terminating the process would work but I am not sure about all the storage and objects used by NotePad - would they all get cleared? Is there another way to close NotePad gracefully? What about clicking the exit menu item with one of the WindowEyes Object methods? Have you closed a app using either a WE method or native VBScript in one of these manners or in some other manner? Rick USA ----- Original Message ----- From: Jeff Weiss To: [email protected] Sent: Sunday, April 24, 2011 3:25 PM Subject: Re: NotePad2011 seems to be good now Your app is now working. That's great!! Now, I have one problem that can come up if you have several notepad files opened at once. Since your file is associated with notepad, each time notepad is started, an instance of your notepad 2011 app is loaded as well. When you then open a duplicate of any of the files that are opened, each instance of your app will fire. That means that you may hear the warning several times. To solve this problem, I recommend that in your next update, you associate the app globally. This means that the app will only run once. It will wait patiently in the background for notepad to be launched. If the app is associated globally, you would only get one warning message when the app detects multiple copies of the same file opened at a time. Hope this helps, jeff weiss ----- Original Message ----- From: RicksPlace To: [email protected] Sent: Sunday, April 24, 2011 6:06 AM Subject: NotePad2011 seems to be good now Hi: I updated everything and uploaded it. I then renamed all my files: NotePad2011.vbs xml and wepm. Then unloaded the original script in appManager, removed the files using AddRemove and renamed NotePad2011.wepm to get ready for a clean install. I used Jamal's install script to install the package. It installed and is working as expected. Not ReAdding the vbs and xml files were causing the problem - the old versions were being ReUploaded. So,it looks like it is working. If you try it out could you let me know if you get the warning if you try and open more than one copy of a NotePad document at the same time? Thanks: Rick USA
