CompositeViewer support: Difference between revisions

Jump to navigation Jump to search
m
Line 42: Line 42:
support for multiple terrain pager threads. We could move to CompositeViewer and support simultaneous views from e.g., the tower, AI
support for multiple terrain pager threads. We could move to CompositeViewer and support simultaneous views from e.g., the tower, AI
models, drones, etc.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17001.html|title=<nowiki>[Flightgear-devel] RFC: changes to views and cameras</nowiki>|author=Tim Moore|date=Thu, 26 Jun 2008 03:53:05 -0700}}</ref>|Tim Moore}}
models, drones, etc.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17001.html|title=<nowiki>[Flightgear-devel] RFC: changes to views and cameras</nowiki>|author=Tim Moore|date=Thu, 26 Jun 2008 03:53:05 -0700}}</ref>|Tim Moore}}
{{cquote|Good thing to have!!!
Just still support graphics context on different screens/displays too ...<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17016.html|title=<nowiki>Re: [Flightgear-devel] RFC: changes to views and cameras</nowiki>|author=Mathias Fröhlich|date=Sat, 28 Jun 2008 00:05:19 -0700}}</ref>|Mathias Fröhlich}}


{{cquote|FG only supports one view position at a time, right? Multiple view positions (e.g. one screen for the tower view and a second screen for
{{cquote|FG only supports one view position at a time, right? Multiple view positions (e.g. one screen for the tower view and a second screen for

Navigation menu