CompositeViewer support: Difference between revisions

Jump to navigation Jump to search
m
→‎Status: https://sourceforge.net/p/flightgear/mailman/message/37075130/
m (→‎Status: https://sourceforge.net/p/flightgear/mailman/message/37075130/)
Line 57: Line 57:


It all builds ok, and he now got fgfs mostly working with CompositeViewer and the usual single View.<ref>https://sourceforge.net/p/flightgear/mailman/flightgear-devel/</ref>
It all builds ok, and he now got fgfs mostly working with CompositeViewer and the usual single View.<ref>https://sourceforge.net/p/flightgear/mailman/flightgear-devel/</ref>
CompositeViewer is not a build-time option any more. It is disabled by default, and enabled on startup with a new --composite-viewer=1 option.<ref>https://sourceforge.net/p/flightgear/mailman/message/37075130/</ref>


Julian made the use of CompositeViewer configurable at runtime, which might simplify getting involved in testing/further development - the same binary can now be used for normal use and for investigating CompositeViewer behaviour.
Julian made the use of CompositeViewer configurable at runtime, which might simplify getting involved in testing/further development - the same binary can now be used for normal use and for investigating CompositeViewer behaviour.

Navigation menu