CompositeViewer support: Difference between revisions

Jump to navigation Jump to search
m (more de-quoting)
Line 81: Line 81:
other screen.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27112.html|title=<nowiki>[Flightgear-devel] Help needed with multi-screen</nowiki>|author=Kavya Meyyappan|date=Fri, 19 Mar 2010 03:31:50 -0700}}</ref>|Kavya Meyyappan}}
other screen.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27112.html|title=<nowiki>[Flightgear-devel] Help needed with multi-screen</nowiki>|author=Kavya Meyyappan|date=Fri, 19 Mar 2010 03:31:50 -0700}}</ref>|Kavya Meyyappan}}


== Known Limitations ==
There are a few limitations of the FlightGear multi-camera/view/display system. Tim Moore is the person who developed this feature (nothing existed before his efforts) and maybe he can offer more insight.  For example, in the case of:
* menus ([[PUI]])
* HUD
* 2d instrument panels
there would need to be some significant code restructuring to allow these to be displayed on other windows.<ref>http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27114.html</ref>
There's a limitation in Plib that forces the GUI to be drawn on one window.<ref>http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27134.html</ref>


== Background ==
== Background ==
{{See also|Canvas Popout Windows}}
{{See also|Canvas Popout Windows}}
{{cquote|I think you have just summarized all the limitations of the FlightGear multi-camera/view/display system.  Tim Moore is the person who developed
this feature (nothing existed before his efforts) and maybe he can offer more insight.  I know that in the case of menus, hud, 2d instrument panels,
there would need to be some significant code restructuring to allow these to be displayed on other windows.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27114.html|title=<nowiki>Re: [Flightgear-devel] Help needed with multi-screen</nowiki>|author=Curtis Olson|date=Fri, 19 Mar 2010 08:36:22 -0700}}</ref>|Curtis Olson}}
{{cquote|there's a limitation in Plib that forces the GUI to be drawn on one window.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27134.html|title=<nowiki>Re: [Flightgear-devel] Help needed with multi-screen</nowiki>|author=Tim Moore|date=Sat, 20 Mar 2010 01:42:31 -0700}}</ref>|Tim Moore}}


{{cquote|That would require a change in current fg architecture to use a CompositeViewer instead of a single Viewer, but we're contemplating that anyway.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17263.html|title=<nowiki>Re: [Flightgear-devel] Cockpit displays (rendering, modelling)</nowiki>|author=Tim Moore|date=Mon, 04 Aug 2008 02:43:52 -0700}}</ref>|Tim Moore}}
{{cquote|That would require a change in current fg architecture to use a CompositeViewer instead of a single Viewer, but we're contemplating that anyway.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17263.html|title=<nowiki>Re: [Flightgear-devel] Cockpit displays (rendering, modelling)</nowiki>|author=Tim Moore|date=Mon, 04 Aug 2008 02:43:52 -0700}}</ref>|Tim Moore}}

Navigation menu