Posted By Paul Kafasis on June 22nd, 2011 Recently, Apple announced that Mac OS X 10.7 (Lion) would ship in July of this year. We’re currently working on providing full support for 10.7 in all of our apps. We’re not there yet, but if you’re curious about what works on 10.7, you can check out the to track our progress.
FlightGear for Mac Download FlightGear Flight Simulator is an open-source flight simulator created by the FlightGear project. Source code for the entire project is available from a CVS repository and licensed under GNU General.
While we can’t guarantee that all of our applications will have full support for 10.7 on the first day Lion is available, they will all be supported on 10.7 as soon as possible. Any updates needed to our current versions will of course be free, so if you’re looking to buy, there’s no need to wait. For now, we recommend our customers stick with Mac OS X 10.6 (Snow Leopard) until 10.7 is actually released. That said, if you are using Lion and our software, please if you run into a bug not mentioned on the. 7 Responses to “Support for Mac OS X 10.7 (Lion)” • skip says: Will Airfoil 3 be updated to work properly with 10.7? I have no real need for the changes added in Airfoil 4 but it’s important that I have 10.7 compatibility. • Paul Kafasis says: Skip: It’s unlikely Airfoil 3 will be updated.
It’s basic functionality will still work, but the Instant Hijack component won’t. You can keep using Airfoil 3, but you’ll want to stick with Mac OS X 10.6. If you’re moving to Mac OS X 10.7, we strongly recommend having the latest Airfoil as well. • Adam says: I know his isn’t the ideal place to post a question but I think many people are wondering. Any idea on an ETA on Airfoil Speakers Touch for Android? • Paul Kafasis says: Adam: Indeed, this isn’t an ideal place at all for many reasons, not least of which is we don’t check these comments with any regularity. We’ve never announced plans for Airfoil Speakers Touch for Android, and still haven’t.
We’ll see what happens, but an ETA for a product we may never make? No, I’m afraid not. • Matt says: I purchased Airfoil 3 and happily upgraded to 4 because I think you guys make a great product. All the while, I have quietly hoped and waited for Android support as, while all of my computers are macs, all of our family phones are Android– and we intend to keep it that way.
Your product is pretty good Android support would make it great. • speedy says: please release a beta/small update when possible that fixes the memory leak, or supply us with beta 4.5 or something. I can live without the instant on and system audio. But would like to keep the basic functionality around for lion. Use it with Peel.app thanks for a great product!
• Paul Kafasis says: Matt: So is it great, or just “pretty good”? 8) Anyhow, it’s something we’re interested in as well, but as I said, it’s certainly not something we’ve ever announced.
We’ll see what happens in the future. Speedy: We don’t have a beta, nor a small update, ready at this time – we’re focused on getting 4.5 out. If the official Lion release beats our release of Airfoil 4.5, we’ll have to consider doing this. Until then, however, sticking with Mac OS X 10.6 is recommended.
$FG_HOME is an environment variable indicating the main location where user-specific FlightGear data is stored (not application data). $FG_HOME is a notable place were FlightGear data is written to, contrary to $FG_ROOT, which is generally read-only. $FG_HOME is normally used to refer to the operating system specific location for some settings/folders. Its default value is determined by the fgfs binary during startup and is a directory that varies with the operating system supported by FG (Windows, OS X and Linux). It is to rely on the default value (i.e., not setting $FG_HOME yourself in any way), unless you Really Know What You Are Doing™. Note The /sim/fg-home property should be considered read-only, for similar reasons why $FG_HOME shouldn't be explicitly set by users.
Note FlightGear reads the config file from $FG_HOME if it exists ( fgfsrc without any leading dot), in addition to.fgfsrc from $HOME (with a leading dot in this case). Contents • • • • • • • • • • • Content In $FG_HOME is information stored between sessions. That information is for example configuration/preferences, properties marked with the user-archive attribute and aircraft-specific settings (using the data helper class in aircraft.nas). $FG_HOME is also the location for the SQLite-based. Common paths You can determine the location of your $FG_HOME by using the and checking the value of /sim/fg-home, but the usual paths are shown below. You can also use the to print out $FG_HOME. Var path = getprop('/sim/fg-home'); print('Your $FG_HOME is at: ', path); The /sim/ property subtree is also the place where you can find other folders, such as fg-root, fg-scenery and the current working directory ( fg-current).
0 kommentar(er)
