Board index FlightGear Development

Announcing FFGo: a new FlightGear launcher

FlightGear is opensource, so you can be the developer. In the need for help on anything? We are here to help you.
Forum rules
Core development is discussed on the official FlightGear-Devel development mailing list.

Bugs can be reported in the bug tracker.

Re: Announcing FFGo: a new FlightGear launcher

Postby rominet » Tue Sep 20, 2016 7:52 pm

One feature you could find useful:
Code: Select all
ffgo --help
usage: ffgo-launcher.py [OPTION ...]
Graphical launcher for the FlightGear flight simulator.

[...]

  -t, --test-mode       enable test mode (useful to test pieces of code from
                        the FFGo GUI)
  -T, --test-only       after startup, run the App.testStuff() method and exit

Both of these run App.testStuff(), which is defined in ffgo/gui/mainwindow.py:
Code: Select all
    def testStuff(self, event=None):
        pass

Put whatever code you want to test there. If you use -t (--test-mode), FFGo will start normally and you can get App.testStuff() to run at the time you want, either from the Tools menu or with Ctrl-T.

You can of course print() stuff to the terminal or use FFGo's logger (look for "logger"). To create windows and other graphical elements, look at examples like the About or Help boxes, and/or a Tkinter tutorial (old but still useful: Fredrik Lundh's tutorial; more recent, very useful document: Tkinter 8.5 reference from John W. Shipman; also, the doc shipped with Python, and when all this fails: Tk docs [not Python-specific]).
rominet
 
Posts: 550
Joined: Sat Nov 01, 2014 1:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: Announcing FFGo: a new FlightGear launcher

Postby rominet » Sun Oct 02, 2016 3:28 pm

For those using my Debian packages: my OpenPGP key, that you have probably fed to apt-key, is about to expire, unless you downloaded it very recently. I don't know if apt would complain (one can hope so), but I am going to tell you how to update the key:
  1. Download the key with an updated expiration date (I use % for non-root user shell prompt):
    Code: Select all
    % wget -O ~/tmp/flo-OpenPGP-key.asc http://frougon.net/OpenPGP-key.asc
  2. Verify its fingerprint:
    Code: Select all
    % gpg2 --with-fingerprint ~/tmp/flo-OpenPGP-key.asc
    pub   rsa4096/0xC785B90B5053A3A2 2010-03-17 [SC] [expires: 2017-10-24]
          Key fingerprint = 125B 5A0F DB78 8FDD 0EF4  1A9D C785 B90B 5053 A3A2
    uid                             Florent Rougon <f.rougon@free.fr>
    uid                             Florent Rougon <flo@via.ecp.fr>
    sub   rsa4096/0xC175ECB11E338EB7 2010-03-17 [E] [expires: 2017-10-24]
          Key fingerprint = D42C 2211 5717 4365 1766  EC10 C175 ECB1 1E33 8EB7

    Note that this command also tells you that the ID of this key is 0xC785B90B5053A3A2 (useful when dealing with keyrings, be it with gpg/gpg2 or apt-key). You can see that the expiration dates are in the future (2017-10-24).
  3. Add the updated key to your apt keyring (this step requires root privileges):
    Code: Select all
    # apt-key add ~/tmp/flo-OpenPGP-key.asc
    OK
While you are at it, you can inspect your apt keyring and possibly remove obsolete keys. The commands 'apt list' and 'apt finger' show neither the key IDs nor their fingerprints, so they are not very useful. However, you can run:
Code: Select all
# apt-key exportall >/some/file/of/your/choice

which exports all keys as a gpg keyring in the file /some/file/of/your/choice. Then inspect what keys are in this file:
Code: Select all
% gpg2 --with-fingerprint /some/file/of/your/choice
pub   rsa4096/0xC785B90B5053A3A2 2010-03-17 [SC] [expires: 2017-10-24]
      Key fingerprint = 125B 5A0F DB78 8FDD 0EF4  1A9D C785 B90B 5053 A3A2
uid                             Florent Rougon <f.rougon@free.fr>
uid                             Florent Rougon <flo@via.ecp.fr>
sub   rsa4096/0xC175ECB11E338EB7 2010-03-17 [E] [expires: 2017-10-24]
      Key fingerprint = D42C 2211 5717 4365 1766  EC10 C175 ECB1 1E33 8EB7
pub   rsa4096/0x7638D0442B90D010 2014-11-21 [SC] [expires: 2022-11-19]
      Key fingerprint = 126C 0D24 BD8A 2942 CC7D  F8AC 7638 D044 2B90 D010
uid                             Debian Archive Automatic Signing Key (8/jessie) <ftpmaster@debian.org>
pub   rsa4096/0x9D6D8F6BC857C906 2014-11-21 [SC] [expires: 2022-11-19]
      Key fingerprint = D211 6914 1CEC D440 F2EB  8DDA 9D6D 8F6B C857 C906
uid                             Debian Security Archive Automatic Signing Key (8/jessie) <ftpmaster@debian.org>
pub   rsa4096/0xCBF8D6FD518E17E1 2013-08-17 [SC] [expires: 2021-08-15]
      Key fingerprint = 75DD C3C4 A499 F1A1 8CB5  F3C8 CBF8 D6FD 518E 17E1
uid                             Jessie Stable Release Key <debian-release@lists.debian.org>
pub   rsa4096/0xAED4B06F473041FA 2010-08-27 [SC] [expires: 2018-03-05]
      Key fingerprint = 9FED 2BCB DCD2 9CDF 7626  78CB AED4 B06F 4730 41FA
uid                             Debian Archive Automatic Signing Key (6.0/squeeze) <ftpmaster@debian.org>
pub   rsa4096/0x64481591B98321F9 2010-08-07 [SC] [expires: 2017-08-05]
      Key fingerprint = 0E4E DE2C 7F3E 1FC0 D033  800E 6448 1591 B983 21F9
uid                             Squeeze Stable Release Key <debian-release@lists.debian.org>
pub   rsa4096/0x8B48AD6246925553 2012-04-27 [SC] [expires: 2020-04-25]
      Key fingerprint = A1BD 8E9D 78F7 FE5C 3E65  D8AF 8B48 AD62 4692 5553
uid                             Debian Archive Automatic Signing Key (7.0/wheezy) <ftpmaster@debian.org>
pub   rsa4096/0x6FB2A1C265FFB764 2012-05-08 [SC] [expires: 2019-05-07]
      Key fingerprint = ED6D 6527 1AAC F0FF 15D1  2303 6FB2 A1C2 65FF B764
uid                             Wheezy Stable Release Key <debian-release@lists.debian.org>

Each time a line starts with 'pub', it marks the start of a new key. Here you can see there is my key, that was manually added as indicated above, and a few Debian archive signing keys automatically managed by apt and friends. Using the following command, you'll see where each of these is located:
Code: Select all
# apt-key list
/etc/apt/trusted.gpg
--------------------
pub   rsa4096 2010-03-17 [SC] [expires: 2017-10-24]
uid           [ unknown] Florent Rougon <f.rougon@free.fr>
uid           [ unknown] Florent Rougon <flo@via.ecp.fr>
sub   rsa4096 2010-03-17 [E] [expires: 2017-10-24]

/etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg
----------------------------------------------------------
pub   rsa4096 2014-11-21 [SC] [expires: 2022-11-19]
uid           [ unknown] Debian Archive Automatic Signing Key (8/jessie) <ftpmaster@debian.org>

/etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg
-------------------------------------------------------------------
pub   rsa4096 2014-11-21 [SC] [expires: 2022-11-19]
uid           [ unknown] Debian Security Archive Automatic Signing Key (8/jessie) <ftpmaster@debian.org>

/etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg
-------------------------------------------------------
pub   rsa4096 2013-08-17 [SC] [expires: 2021-08-15]
uid           [ unknown] Jessie Stable Release Key <debian-release@lists.debian.org>

/etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg
-----------------------------------------------------------
pub   rsa4096 2010-08-27 [SC] [expires: 2018-03-05]
uid           [ unknown] Debian Archive Automatic Signing Key (6.0/squeeze) <ftpmaster@debian.org>

/etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg
--------------------------------------------------------
pub   rsa4096 2010-08-07 [SC] [expires: 2017-08-05]
uid           [ unknown] Squeeze Stable Release Key <debian-release@lists.debian.org>

/etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg
----------------------------------------------------------
pub   rsa4096 2012-04-27 [SC] [expires: 2020-04-25]
uid           [ unknown] Debian Archive Automatic Signing Key (7.0/wheezy) <ftpmaster@debian.org>

/etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg
-------------------------------------------------------
pub   rsa4096 2012-05-08 [SC] [expires: 2019-05-07]
uid           [ unknown] Wheezy Stable Release Key <debian-release@lists.debian.org>

Given the key ID shown by the 'gpg2 --with-fingerprint' command above, you could remove my key from your apt keyring like this if you wanted:
Code: Select all
# apt-key del 0xC785B90B5053A3A2

Note: you should probably not remove Debian archive signing keys like this, except if you added some yourself manually.
rominet
 
Posts: 550
Joined: Sat Nov 01, 2014 1:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: Announcing FFGo: a new FlightGear launcher

Postby rominet » Mon Nov 14, 2016 3:14 pm

Hello,

I am pleased to announce the release of FFGo 1.12.1. The most important things to know for users upgrading to this version are:
  • Don't use --download-dir nor --terrasync-dir anymore inside the Options Window (the large text field on white background located on the left of FFGo's main window); use the Download directory setting in the Preferences dialog instead;
  • A few other options (--timeofday, --season, --enable-terrasync, --enable-fullscreen, --enable-freeze, --enable-rembrandt and two --prop settings to enable multi-sample anti-aliasing) are now easily accessible using graphical controls in the main window (see screenshot below). While it is not forbidden to set them conditionally using CondConfigParser syntax, it doesn't make sense anymore in most cases since the new checkboxes will add them for you. So, unless you have specific needs such as conditionally setting the time of day, or conditionally enabling or disabling Rembrandt, etc., you should probably just remove these settings from your Options Window too (and if you have such a need, you'll probably want to add these options to MERGED_OPTIONS, as explained in the FFGo conditional config documentation).
With that said, the main changes since version 1.11.3 are:
  • Support reading and merging of in-scenery-paths apt.dat files.
    • Adapt to the new feature introduced in FlightGear commit 516a5cf0 (committed on October 17, 2016) that allows FlightGear to read and merge an arbitrary number of uncompressed or gzip-compressed apt.dat files located in the NavData/apt subdirectory of each scenery path (plus, at least for now, the usual $FG_ROOT/Airports/apt.dat.gz considered with lowest priority).
    • Users of FlightGear 2016.4.0 must have their FlightGear more recent than November 9, 2016 (FlightGear commit fb10f76e). For FlightGear 2016.3.x or older, only $FG_ROOT/Airports/apt.dat.gz is read (old behavior).
  • Introduce a new Download directory setting, tunable from the Preferences dialog.

    This was necessary, because the directory specified with the --download-dir fgfs option contributes a scenery path when TerraSync is enabled (download_dir/TerraSync except when --terrasync-dir is used, but this last option is not very useful, only kept as legacy since --download-dir was added to FlightGear).

    IMPORTANT

    As explained above, using --download-dir or --terrasync-dir inside the Options Window is not supported anymore, as doing this correctly would potentially require to rebuild the apt digest file every time a character is added to, or removed from the corresponding line in the Options Window. To compensate for this, users can set the download directory in the Preferences dialog.

    Print an explanatory message when trying to use --download-dir or --terrasync-dir in the Options Window.
  • Add a progress bar to the window displayed when rebuilding the apt digest file/airport database.
  • Add config parameters and drop-down lists for the season (summer or winter textures) and time of day.
  • Add Enable automatic scenery download (i.e., TerraSync), Start FlightGear in full screen, Start FlightGear paused, Enable multi-sample anti-aliasing and Enable deferred rendering (Rembrandt) configuration parameters and check buttons.
  • Try to simplify and make more understandable the logic deciding when to rebuild the apt digest file (especially in automatic mode).
  • Small fix in Config._findInstalledApt() (used for the Show installed airports only feature, when choosing Update list of installed airports in the Settings menu).

    In the corner case where TerraSync is enabled and the TerraSync directory isn't listed in Config.FG_scenery, then FlightGear is going to use it as a scenery path, so visiting Config.FG_scenery only was not quite right. This is fixed for FlightGear versions that have --json-report (option which appeared in FlightGear 2016.4.0, commit fb10f76e from November 9, 2016).

    Anyway, I recommend to always explicitly list the TerraSync directory in Config.FG_scenery: this is IMHO more logical, and the resulting behavior is more predictable. Otherwise, the list of scenery paths used by FlightGear can change whenever you enable or disable TerraSync—eeek!
  • Disable the error popup dialog when parsing broken groundnet files.

    This dialog box was quite ugly and annoying, and didn't have the effect I hoped (i.e., people fixing the groundnet files—at least, not in many airports distributed via TerraSync).

    The errors are still logged to the terminal and to FFGo's log file for those who care about providing sane groundnet files.
  • Print a helpful message when the fallback localization file ffgo/data/locale/en/LC_MESSAGES/FFGo.mo can't be found. This happens every time someone tries to run FFGo from the Git repository without preparing it as per the instructions in docs/INSTALL/INSTALL_en. And then people think it's a bug... This message should help prevent such confusion.
  • Update the FFGo conditional config documentation (aka README.conditional-config).
    • Don't use options such as --timeofday, --season, --enable-fullscreen, --enable-terrasync and --terrasync-dir in the examples, since these are now specifically managed by FFGo, thus using them in the Options Window is redundant and confusing (e.g., if a checkbox is unchecked but the corresponding option is added from the Options Window).
    • Give a hint about how to automatically load specific joystick binding files depending on the aircraft (this is in an example regarding helicopters, using the 'heli_class' CondConfigParser variable).
  • Update changed URL to retrieve METAR reports. The old URL doesn't work anymore, use this one instead. I thought FFGo wasn't affected (thinking some HTTP redirection was doing its job), and since nobody reported the problem... well, it is fixed now.
  • Update the German translation (thanks to chris_blues, as usual!).
As usual, you can get this release from FFGo's home page. Debian packages for jessie and unstable are available from there too, along with the distribution-agnostic tarballs and zip files.

Please report any problem you find (the apt.dat-related changes were not completely trivial; I did test them, but one or two bugs might still remain, one never knows).

P.S.: for users of my Debian packages, if you see something like this:
Code: Select all
WARNING: untrusted versions of the following packages will be installed!

Untrusted packages could compromise your system's security.
You should only proceed with the installation if you are certain that
this is what you want to do.

  python3-condconfigparser
  ffgo

it means you should read this message to provide apt with an updated OpenPGP key.

Enjoy.

Image
rominet
 
Posts: 550
Joined: Sat Nov 01, 2014 1:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: Announcing FFGo: a new FlightGear launcher

Postby rominet » Thu Nov 24, 2016 4:44 pm

Hello,

I have released FFGo 1.12.2. The main changes in this version are:
  • Layout improvements in the main window. The goal is to increase the likelihood of the main window fitting on screens that are not very wide (1280 pixels wide with font size 11 should now be OK in English as well as in French—this of course depends on the particular fonts used).
  • Use a Ttk PanedWindow for the top part of the main window, thus allowing users to choose how to distribute horizontal space in the top “row” containing the aircraft list, the two middle panes and the airport list (at run time, using the mouse).
  • (this item is only for advanced users, most people can skip it)
    Stricter check for FlightGear versions having the --json-report option. Now that FlightGear 2016.4.1 is out, check for this version rather than 2016.4.0, because 2016.4.1 guarantees the availability of --json-report while 2016.4.0 does not (only the very last FG commits labelled 2016.4.0 have this option).

    As a consequence, FFGo will now read apt.dat files inside scenery_path/NavData/apt directories (for each scenery path, in addition to $FG_ROOT/Airports/apt.dat.gz) if, and only if the FlightGear version is 2016.4.1 or later. With older FlightGear versions, only $FG_ROOT/Airports/apt.dat.gz is used. The little change here is that FFGo 1.12.1 tried to read the scenery_path/NavData/apt files also if the FlightGear version was 2016.4.0, which would only work with the latest commits of the FG 2016.4.0 development “version” (which is not really a FlightGear version, but rather a range of commits leading to 2016.4.1).
  • Small addition to the FFGo conditional config documentation (ATCChatter example).
As usual, you can get this release from FFGo's home page. Debian packages for jessie and unstable are available from there too, along with the distribution-agnostic tarballs and zip files.
rominet
 
Posts: 550
Joined: Sat Nov 01, 2014 1:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: Announcing FFGo: a new FlightGear launcher

Postby rominet » Sun Nov 27, 2016 11:55 pm

I realized not passing --enable-terrasync to fgfs is not enough to disable TerraSync (FG remembers when TerraSync has been used...), therefore unchecking Automatic scenery download in the last release may not have the desired effect. This is fixed in the Git repository. I also added a configuration parameter and check box to enable or disable real weather fetch—mainly because it is convenient to speed up FG debugging sessions.
rominet
 
Posts: 550
Joined: Sat Nov 01, 2014 1:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: Announcing FFGo: a new FlightGear launcher

Postby rominet » Wed Dec 07, 2016 11:20 am

Hello,

I have released FFGo 1.12.3 (which could have been versioned 1.13.0...). The changes are essentially what I described in the previous message, namely:
  • Pass --disable-terrasync when automatic scenery download is disabled. Omitting --enable-terrasync is not enough, FlightGear remembers the setting!
  • Add a configuration parameter and check box in the main window to enable or disable automatic download of weather data (also known as “real weather fetch”). This is convenient when one repeatedly runs FlightGear to debug something and wants it to start as quickly as possible.
  • Small layout adjustments in FFGo's main window.
  • Rewording of the MSAA tooltip: it doesn't seem to impact frame rate that badly.
As usual, you can get this release from FFGo's home page. Debian packages for jessie and unstable are available from there too, along with the distribution-agnostic tarballs and zip files.
rominet
 
Posts: 550
Joined: Sat Nov 01, 2014 1:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: Announcing FFGo: a new FlightGear launcher

Postby rominet » Sat Mar 11, 2017 7:32 pm

I have released FFGo 1.12.4 with a tiny change in a comment of the default config, and an updated German translation (thanks to chris blues).
rominet
 
Posts: 550
Joined: Sat Nov 01, 2014 1:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: Announcing FFGo: a new FlightGear launcher

Postby pommesschranke » Sat Mar 11, 2017 11:22 pm

I have a feature suggestion:

* ffgo may remember the parking spot that the user did choose the last time when starting at an airport.
pommesschranke
 
Posts: 1100
Joined: Sat Apr 27, 2013 7:58 pm
Location: EDLM & LJCE
Callsign: d-laser
IRC name: laserman
Version: git
OS: Linux Lubuntu 18.04

Re: Announcing FFGo: a new FlightGear launcher

Postby chris_blues » Sun Mar 12, 2017 3:45 am

Nice one! But wow! Here comes the next database! I don't know! I loved FFGo for it's responsiveness, once it's started. Let's not make it too "smart" (or should I say fat?)

\o/ Whoopie for a new release! :D
Don't hesitate to let me know if I'm incorrect or just annoying! As long as you do it gently! :)
Debian testing 64bit - Athlon II 2x2.6GHz - 8GB RAM - GeForce GTS 450
Citation II
User avatar
chris_blues
 
Posts: 1526
Joined: Mon May 03, 2010 1:30 pm
Location: claws of real life
Callsign: chris_blues
Version: GIT
OS: Debian 8 64

Re: Announcing FFGo: a new FlightGear launcher

Postby rominet » Sun Mar 12, 2017 1:58 pm

Mmmmm, yes, so I take it Mr. pommesschranke has a reserved parking position in his name at several airports. I see. :wink:

I think this would go relatively painlessly in ~/.ffgo/Stats/airports.json.gz (%APPDATA%/FFGo/Stats/airports.json.gz on Windows), but would require a new format version for this file. And quite desirably automatic conversion from the old to the new format. Unfortunately, I haven't planned the transition perfectly, so users who, after such a change, downgrade their FFGo but keep ~/.ffgo/Stats/airports.json.gz will have an error until they move this file to a different place. Well...

I don't rule this out, but can't promise it for soon either, as I have a few other things in the oven and RL doesn't give me much latitude to do them...
rominet
 
Posts: 550
Joined: Sat Nov 01, 2014 1:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: Announcing FFGo: a new FlightGear launcher

Postby wkitty42 » Sun Mar 12, 2017 2:57 pm

FWIW (with a little fun poking): the --launcher remembers (at least) the last ten airports and starting positions... it also remembers (at least) the last ten craft selected and flown... those numbers may be fifteen or twenty but i know that the boxes hold lists of quite a few previously selected ;) :)
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 4762
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Announcing FFGo: a new FlightGear launcher

Postby rominet » Sun Mar 12, 2017 4:50 pm

If you look at FFGo's screenshots, you should see it has been doing that for a long time... it is even used for the default sorting of the airports and aircraft lists (by how many days you've visited/used a given airport/aircraft during a customizable time period).

From what I understand of pommesschranke's request, --launcher doesn't do it either (i.e., if you start at LOWI stand A5, then quit, start at another airport, quit again, start again at LOWI, then stand A5 could be automatically selected). It's for people who can't remember which stand they have rented. :roll:
rominet
 
Posts: 550
Joined: Sat Nov 01, 2014 1:33 pm
Callsign: F-KATS
Version: Git next
OS: Debian GNU/Linux

Re: Announcing FFGo: a new FlightGear launcher

Postby pommesschranke » Sun Mar 12, 2017 6:54 pm

rominet wrote in Sun Mar 12, 2017 4:50 pm:
From what I understand of pommesschranke's request, --launcher doesn't do it either (i.e., if you start at LOWI stand A5, then quit, start at another airport, quit again, start again at LOWI, then stand A5 could be automatically selected). It's for people who can't remember which stand they have rented. :roll:


correct. --launcher doesn't do that. Xplane11 does it. ;-)

I use FFGo every day.
--launcher is nice, too!
The graphical way of choosing runway/parking is nice.
But the way that FFGo is presenting them sorted by type is nice, too.

The ability to add 3rd party aircraft hangars and install from them is cool, but I never use it ;-)
Will it show me when there is a newer version of an aircraft in the repo compared to my current version ?

What don't like about --launcher:
* when I close flightgear, the launcher also dies. (Maybe not so bad when I make a "fgfs --launcher" icon. )
With FFGo I can change options for the next fg start even when fg is still running.
* I can add custom sceneries but I cannot temporarily disable them, only completely remove.
.. but I can add --fg-scenery=.. lines with and without "#" to "Additional options" in the same way I do it with FFGo. that's nice!

I like them both.
pommesschranke
 
Posts: 1100
Joined: Sat Apr 27, 2013 7:58 pm
Location: EDLM & LJCE
Callsign: d-laser
IRC name: laserman
Version: git
OS: Linux Lubuntu 18.04

Re: Announcing FFGo: a new FlightGear launcher

Postby wkitty42 » Sun Mar 12, 2017 11:43 pm

rominet wrote in Sun Mar 12, 2017 4:50 pm:If you look at FFGo's screenshots, you should see it has been doing that for a long time... it is even used for the default sorting of the airports and aircraft lists (by how many days you've visited/used a given airport/aircraft during a customizable time period).

like i said, some fun poking ;)

rominet wrote in Sun Mar 12, 2017 4:50 pm:From what I understand of pommesschranke's request, --launcher doesn't do it either (i.e., if you start at LOWI stand A5, then quit, start at another airport, quit again, start again at LOWI, then stand A5 could be automatically selected). It's for people who can't remember which stand they have rented. :roll:

then i'm missing something... i load at KJFK A11... quit... load somewhere else... quit... load at KJFK terminal 31L Area 111... quit... load again... now, in the summary TAB, i can select from "KJFK A11" or "KJFK terminal 31L Area 111" from the button to the far right of the location... i can choose one of the previous X craft i've flown by using the button to the far right of the craft entry, too...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 4762
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

Re: Announcing FFGo: a new FlightGear launcher

Postby biloute974 » Mon Mar 13, 2017 6:51 am

Would it be possible to create a button that records / recalls the last position of the aircraft?
Intel I7 7700 - 16Gb DDR4 - Nvidia GTX970 - FG 2017.4.0 from D&C
biloute974
 
Posts: 180
Joined: Mon Feb 23, 2015 8:49 am
Callsign: U974
Version: 2016.1.0
OS: Mint 17.2

PreviousNext

Return to Development

Who is online

Users browsing this forum: No registered users and 1 guest