20,741
edits
FlightGear Qt launcher: Difference between revisions
Jump to navigation
Jump to search
no edit summary
mNo edit summary |
No edit summary |
||
| Line 18: | Line 18: | ||
All of this would be a QtQuick 2 GUI, not a Qt widgets GUI. If you don’t know what that terminology means, don’t worry about it, the quick answer is it works the same ways as Canvas does at present (rendering to OpenGL). | All of this would be a QtQuick 2 GUI, not a Qt widgets GUI. If you don’t know what that terminology means, don’t worry about it, the quick answer is it works the same ways as Canvas does at present (rendering to OpenGL). | ||
The replacement launcher is very young, so we apologise for any functionality gaps. In general it emphasises setting only the things that cannot be changed at runtime, and some common general settings (real weather, time of day, location). That’s why anti-aliasing and Rembrant are exposed but not multi-player settings, since the in-sim UI works perfectly for those features. The same is true for scenarios and AI traffic. <ref>http://sourceforge.net/p/flightgear/mailman/message/33464757/</ref> | |||
For now, the goal is to make an '''optional''' Qt dependency to replace PLIB PUI. Except of course PUI will have to remain for some awkward use cases in the short term (aircraft dialogs, potentially). When compiled without Qt support, you’ll get a fully functional FG (i.e., Qt will never be a requirement to build FG), but without the GUI functions – which is indeed what some people want anyway (e.g., in some home cockpit setups). | For now, the goal is to make an '''optional''' Qt dependency to replace PLIB PUI. Except of course PUI will have to remain for some awkward use cases in the short term (aircraft dialogs, potentially). When compiled without Qt support, you’ll get a fully functional FG (i.e., Qt will never be a requirement to build FG), but without the GUI functions – which is indeed what some people want anyway (e.g., in some home cockpit setups). | ||