20,741
edits
Aircraft Center: Difference between revisions
Jump to navigation
Jump to search
m
RFEs
m (RFEs) |
|||
| Line 78: | Line 78: | ||
So, the most natural thing to do would be to '''directly integrate these facilities into FlightGear''', where they can make use of extensive FlightGear APIs that are known to compile and work across all supported FlightGear platforms. | So, the most natural thing to do would be to '''directly integrate these facilities into FlightGear''', where they can make use of extensive FlightGear APIs that are known to compile and work across all supported FlightGear platforms. | ||
== Feature Requests == | |||
=== Supporting separate/external Windows for the GUI === | |||
{{FGCquote | |||
|This looks promising in a technical/coding perspective of having this and that common GUI feature available also for flightgear. But for me personally one of the big problems of the FlightGear GUI is that it is "inside" the only and one main window. There is no possibility to have a separate window to not cover the main content, the scenery and the cockpit? This would make the GUI much more practical. I would really like to run flightgear with one window "view" and other windows for the program (options). This will improve the usability of all the menus, dialogs etc. a lot in my opinion. | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/29586327/ | |||
|title=<nowiki>Re: [Flightgear-devel] Switching from PUI to osgWidget</nowiki> | |||
|author=<nowiki>ys</nowiki> | |||
|date=<nowiki>2012-07-24</nowiki> | |||
}} | |||
}} | |||
== Status == | == Status == | ||
{{cquote | {{cquote | ||