Hi James



Am 12.08.2012 um 17:48 schrieb James Turner <zakal...@mac.com>:

> 
> On 11 Aug 2012, at 22:52, Martin Spott wrote:
> 
>>> 3) Scenery.  Terrasync is now built into FG, and we have nice UI to
>>> configure it in-sim.  However, it still requires users to set up a
>>> separate directory and configure FG_SCENERY before it can be used.  It
>>> would be great if the standard installers created an
>>> $FG_ROOT/WorldScenery directory with the appropriate permissions, and
>>> added it to $FG_SCENERY by default.
>> 
>> As far as I can tell, the value of "/sim/terrasync/scenery-dir" was
>> already supposed to be added to the Scenery path, but I don't know at
>> which priority.
> 
> Right, this is all automatic now - has been since before 2.6 I think. At 
> least on Mac I set a 'correct' directory - in Library/Application 
> Support/FlightGear/Terrasync. Of course this is only a default, but for most 
> users it's enough.

This is one of the 'correct' places of course. With FGx I put this folder 
(which I do not name "terrasync", I create a folder "TerrasyncScenery" or 
"TerrasyncData") into Users/Shared by default because of different reasons. One 
reason is that for the "common" user the Library Folder is hidden by default 
now on osx, the other reason is wanted to have an easy shareable place for 
different machines, so I don't need to terrasync for every machine.

Because the Application Support directory is hidden  by default I fear there 
will be some other posts in the forums soon "where is my terrasynced scenery", 
but maybe it's better to have a correct place then my not-so-correct FGx way 
for osx ;-)

Do for consistency reasons it might be good to follow your changes here.

Thanks, Yves


> 
> If there's bugs / edge-cases that are not working, please report them and 
> they should be fixable, possibly with a couple of extra configuration options.
> 
> Usability was the main reason for making terrasync be available as in-process 
> option, and I'm strongly considering doing the same thing for fgcom, although 
> that has a few extra complications.
> 
> BTW, usability is also the reason I made the network options configurable 
> inside the sim, and have been making more subsystems support a clean reset, 
> so that it's possible to sanely control more behaviours with direct results 
> in the sim.
> 
> James
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to