Melchior FRANZ wrote: > On Sun, Jan 15, 2006 at 03:40:41PM -0600, Curtis L. Olson wrote: > >>We also should also think about picking a file name that more clearly >>indicates that this is something reserved for the FlightGear app to use, >>not for user customizations. > > > I had suggested ~/.fgfs/autosave.xml ... several times, > without success. :-} > > m. > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Flightgear-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/flightgear-devel >
Sigh. Oh well, at least there is an easy fix. I'm all set now, but I fear that this will cause confusion in the future. I like your idea though Melchior, one file for me, one for flightgear. Or even put the autosave stuff in a section of preferences that has a big comment on it explaining where it came from. I don't have a problem with fg putting stuff into my preferences.xml, that is a pretty common practice with configuration software. The problem is the stuff it took out. And to add insult to injury, the idea of persistent configuration changes is good, but it looks like I can't take advantage of it unless I give up my custom configuration. Josh ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
