Greetings Listers, I Also agree with Ian and Peter. I prefer to use ini-files instead of the registry.
I code my programs to generate a Default ini file if it can't find it, or it becomes corrupt or accidently deleted. This also has the advantage that, if the user changes things in the ini file and stuffs it up, you can get them to delete the ini file, re-run the mbx and they have a new Default ini file. Regards Peter Doyle Geographical Analysis & Data Mobile Coverage Delivery: Service Management Solutions. Ph: 07 3887 1128; Mob: 0418 709 250 Fax: 07 32364383 Email: <mailto:[EMAIL PROTECTED]> -----Original Message----- From: Peter Horsb�ll M�ller [mailto:[EMAIL PROTECTED] Sent: Thursday, September 16, 2004 7:18 AM To: Ian Tidy; Bill Thoen Cc: MapInfo-L Subject: RE: MI-L OT - Windows Programming Philosophy I agree with Ian ! I also prefer to use ini-files instead of the registry. Another good thing about the ini file is that if you have your application placed on a central server, you can put a default ini file with your application. If the application can't locate a ini file on the locale computer, it reads the central ini file to get the default values. And as Ian noted it is easier to let the user change things in a ini file and send a ini file to me to look at. Just my 5 �rer, Peter Horsb�ll M�ller GIS Developer Geographical Information & IT COWI A/S Odensevej 95 DK-5260 Odense S. Denmark Tel +45 6311 4900 Direct +45 6311 4908 Mob +45 5156 1045 Fax +45 6311 4949 E-mail [EMAIL PROTECTED] http://www.cowi.dk/gis -----Original Message----- From: Ian Tidy [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 15, 2004 11:11 PM To: 'Bill Thoen' Cc: MapInfo-L Subject: RE: MI-L OT - Windows Programming Philosophy Hi Bill, Personally, I can't stand the registry. It get so full of crap the it is impossible to navigate. I have also read that INI files are no longer recommended. But I choose to ignore this fact and store all my settings in INI files in the application directory. This way I know exactly where my file is and what is in it, and I have full control over it. If I need the end user to make a change, I know without a doubt that they can't stuff any other program. I think it is personal preference, and I prefer not to use the registry. Cheers Ian -----Original Message----- From: Bill Thoen [mailto:[EMAIL PROTECTED] Sent: Thursday, 16 September 2004 9:08 a.m. To: MapInfo-L Subject: MI-L OT - Windows Programming Philosophy While developing some MapBasic code to support Windows API calls to access private profile files (see http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/bas e/registry_functions.asp?frame=true) I ran across a Microsoft warning that says that using private profiles (those *.ini files) is no longer in fashion and that now we should always use the Registry to store parameters for programs. My feeling is that the Registry is already pretty stuffed with loose toys, and putting everything into that one system is unwise. However, I don't want to let my ignorance get me into trouble someday, so I thought I'd ask for opinions. What do other developers think about using the Registry instead of ini files for MapBasic apps? Is it a black and white issue, or ar there reasons for using an ini file sometimes, and the Registry at other times? Is a centralized repository of configuration data a better model than using distributed ones? Does anyone have any good arguments pro or con on this? Or should we do it simply because Microsoft says so? I suppose if they've lost interest in ini files, it might be a good idea to not to use them. - Bill Thoen --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 13357 ###################################################################### This e-mail message has been scanned and cleared by MailMarshal ###################################################################### ###################################################################### Attention: This e-mail message and accompanying data may contain information that is confidential and subject to legal privilege. Any information provided is given in good faith. However unless specifically stated to the contrary, Napier City Council accepts no liability for the content of this e-mail or for the consequences of any action taken on the basis of the information provided, unless that information is subsequently confirmed in writing. If you are not the intended recipient, you are notified that any use, dissemination, distribution or copying of this message or data is prohibited. If you received this e-mail message in error, please notify us immediately and erase all copies of this message and attachments. Thank you. --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 13359 --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 13361 --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 13367
