Questions and discussion about creating aircraft. Flight dynamics, 3d models, cockpits, systems, animation, textures.
by Richard » Fri Nov 02, 2018 6:29 am
it0uchpods wrote in Thu Nov 01, 2018 11:13 pm:Then I suggest adding an option to the confirm dialog if opened from the OS to exit without autosaving.
It's not that simple as I just checked and it is OSG that is handling the WM_CLOSE and it doesn't look simple to intercept this and prompt the user.
-
Richard
-
- Posts: 680
- Joined: Sun Nov 02, 2014 10:17 pm
- Version: Git
- OS: Win10
-
by wlbragg » Tue Nov 06, 2018 9:29 pm
We're getting ready to revamp the way saved data and states are currently handled in order to correctly use the QT-launcher options. We can evaluate the need (or not) of how to handle window close (X) command at that time.
Kansas(2-27-15)/
Ohio/Midwest scenery development.
KEQA (2-27-15), 3AU, KRCP Airport Layout
-
wlbragg
-
- Posts: 4551
- Joined: Sat Aug 25, 2012 11:31 pm
- Location: Kansas (Tornado Alley), USA
- Callsign: WC2020
- Version: next
- OS: Win10/Debain/nVGT640
by Knüppelrührer » Sat Jan 12, 2019 2:11 pm
I have tried (FGFS 3.1, stock C172) system failures and both pitot and and vacuum failures cannot be activated. Other items are fine. Can anyone confirm on his installation?
-
Knüppelrührer
-
- Posts: 48
- Joined: Thu Oct 25, 2018 9:06 pm
Return to Aircraft
Who is online
Users browsing this forum: Baidu [Spider], Google [Bot], ronh and 4 guests
FlightGear Forum