20,741
edits
Howto:Configure camera view windows: Difference between revisions
Jump to navigation
Jump to search
m
Howto:Configure camera view windows (view source)
Revision as of 16:46, 12 February 2015
, 12 February 2015no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 37: | Line 37: | ||
Let's first look at an example, setting up two extra windows. Add something like the following code to the <rendering> section of your preferences.xml file: | Let's first look at an example, setting up two extra windows. Add something like the following code to the <rendering> section of your preferences.xml file: | ||
<syntaxhighlight lang="xml"> | |||
<camera> | <camera> | ||
<host-name type="string"></host-name> | <host-name type="string"></host-name> | ||
| Line 57: | Line 58: | ||
<fullscreen type="bool">false</fullscreen> | <fullscreen type="bool">false</fullscreen> | ||
</camera> | </camera> | ||
</syntaxhighlight> | |||
To simplify maintenance you can also save these modifications in a separate PropertyList-encoded XML file (i.e. toplevel XML node must be named "PropertyList") and simplly reference it in preferences.xml by making use of the include attribute in the <rendering section>. | To simplify maintenance you can also save these modifications in a separate PropertyList-encoded XML file (i.e. toplevel XML node must be named "PropertyList") and simplly reference it in preferences.xml by making use of the include attribute in the <rendering section>. | ||
| Line 62: | Line 64: | ||
Preferences.xml will look like this: | Preferences.xml will look like this: | ||
<syntaxhighlight lang="xml"> | |||
<rendering include="camera-views.xml"> | <rendering include="camera-views.xml"> | ||
... | ... | ||
</rendering> | </rendering> | ||
</syntaxhighlight> | |||
And a to be created camera-views.xml file will have the following content: | And a to be created camera-views.xml file will have the following content: | ||
<syntaxhighlight lang="xml"> | |||
<?xml version="1.0"?> | <?xml version="1.0"?> | ||
<PropertyList> | <PropertyList> | ||
| Line 90: | Line 97: | ||
</camera> | </camera> | ||
</PropertyList> | </PropertyList> | ||
</syntaxhighlight> | |||
Finally, you may be better off just running a separate FlightGear instance on the second monitor and slaving it. The whole idea behind having a multiple screen setup like twinview is that it mimicks a continuous area with no boundaries. Putting those screen boundaries back in when the video subsystem has worked so hard to eliminate them is a metaphor collision and a design problem, see [[Property Tree/Native Protocol Slaving]]. | Finally, you may be better off just running a separate FlightGear instance on the second monitor and slaving it. The whole idea behind having a multiple screen setup like twinview is that it mimicks a continuous area with no boundaries. Putting those screen boundaries back in when the video subsystem has worked so hard to eliminate them is a metaphor collision and a design problem, see [[Property Tree/Native Protocol Slaving]]. | ||