Yup, completely agreed <smile>.
-----Original Message----- From: Doug Geoffray [mailto:[email protected]] Sent: Wednesday, February 01, 2012 10:27 AM To: [email protected] Subject: Re: Device Status app update Jeff, Sure, it just depends on the extent of the "damage" that needs to be resolved. As I mentioned, you can try and resolve the .ini or just nuke it. I took the easy path given I only have 2 hotkeys which rarely get changed <smile>. Doug On 2/1/2012 11:40 AM, Jeff Bishop wrote: > The code in my apps doesn't delete the INI but keeps the custom > hotkeys in place that users may have had but also removes un-used > hotkeys and adds new ones as new versions of the app come out. > > > -----Original Message----- > From: Doug Geoffray [mailto:[email protected]] > Sent: Wednesday, February 01, 2012 9:39 AM > To: [email protected] > Subject: Re: Device Status app update > > Vic, > > Yes, I do this in weevent. Here is the code at the top of the .vbs file: > > ' if our .ini file doesn't have my specific version set correctly then > it is an old ' .ini file. Because of conflicts lets just delete the > old and start with a fresh ' empty one. > If IniFile(weeventINI).Number(optionsSectionName, "my_ini_version", 0) > = > 0 Then > If fso.FileExists(WeeventINI) Then > fso.DeleteFile weeventINI, TRUE > End If > IniFile(weeventINI).Number(optionsSectionName, "my_ini_version") > = 1 End If > > > Regards, > Doug > > > On 2/1/2012 11:34 AM, Vic Beckley wrote: >> Doug, >> >> The reason I had problems with the *.ini file is that I deleted some >> hotkeys. When the standard register hotkeys subroutine ran it found > hotkeys >> in the old INI file that didn't exist. This caused an error. What is >> the best way to handle this? Is there an app with examples I can look >> at that you are aware of? >> >> >> -----Original Message----- >> From: Doug Geoffray [mailto:[email protected]] >> Sent: Wednesday, February 01, 2012 10:33 AM >> To: [email protected] >> Subject: Re: Device Status app update >> >> Vic, >> >> I never liked the idea of having to remove older .ini files. I know >> Aaron likes this method (smile). A very simple way that I've gotten >> around this is just put a version entry in your .ini. You would >> first verify the version is correct and if not you can clean it up or >> just delete it if necessary but you will certainly need to add the >> updated version to your cleaned up one or your newly created one. >> This way you'll always just work. >> >> Doug >> >> On 1/31/2012 12:45 PM, Vic Beckley wrote: >>> Hi all, >>> >>> I have updated the Device Status app. I updated my E-mail address >>> and >> added >>> a Device Status submenu on the Apps menu in the window-eyes control > panel. >>> Device Manager has to be running to see this menu. >>> >>> Important: You will have to delete your devicestatus.ini file before >>> installing this update or you will get an error. >>> >>> If there are any problems, let me know. >>> >>> >>> Best regards from Ohio, U.S.A., >>> >>> Vic >>> E-mail: [email protected] >>> >>> >>> >
