20,741
edits
Canvas troubleshooting: Difference between revisions
Jump to navigation
Jump to search
m
→Patching CanvasMgr to use CompositeViewer internally
| Line 701: | Line 701: | ||
=== Patching CanvasMgr to use CompositeViewer internally === | === Patching CanvasMgr to use CompositeViewer internally === | ||
{{cquote|A moving map is a different beast. It would make sense to implement that as a scene graph in its own right<ref>{{cite web |url=https://www.mail-archive.com/flightgear-devel%40lists.sourceforge.net/msg17263.html|title=Cockpit displays (rendering, modelling)|author=Tim Moore |date=Mon, 04 Aug 2008 02:43:52 -0700}}</ref>|Tim Moore }} | |||
{{cquote|I believe that we need to distinguish between different render to texture cameras. Camera nodes must be accessible from within flightgear. That ones that will end in mfd displays or hud or whatever that is pinned into models. And one that are real application windows like what you describe - additional fly by view, and so on. And I believe that we should keep that separate and not intermix the code required for application level stuff with building of 3d models that do not need anything application level code to animate the models ... I think of some kind of separation that will also be good if we would do HLA between a viewer and an application computing physical models or controlling an additional view hooking into a federate ...<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel%40lists.sourceforge.net/msg17026.html|title=RFC: changes to views and cameras|author=Mathias Fröhlich |date=30 Jun 2008 22:46:34 -0700}}</ref>|Mathias Fröhlich }} | {{cquote|I believe that we need to distinguish between different render to texture cameras. Camera nodes must be accessible from within flightgear. That ones that will end in mfd displays or hud or whatever that is pinned into models. And one that are real application windows like what you describe - additional fly by view, and so on. And I believe that we should keep that separate and not intermix the code required for application level stuff with building of 3d models that do not need anything application level code to animate the models ... I think of some kind of separation that will also be good if we would do HLA between a viewer and an application computing physical models or controlling an additional view hooking into a federate ...<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel%40lists.sourceforge.net/msg17026.html|title=RFC: changes to views and cameras|author=Mathias Fröhlich |date=30 Jun 2008 22:46:34 -0700}}</ref>|Mathias Fröhlich }} | ||