OK, Melchior and Jim, you're both right.
The actual problem was my error: the <number-views> was one less than
the actual number of views. Sorry to waste bandwidth on a user error...
Looking back at his message, Melchior was trying to tell me this, but
it flew right past me, so to speak. Jim is right that it was not
replacing one of flightgear's default views that caused the problem.
I must have forgot to change <number-views> when I updated a new base
package with my changes, imagine that! 8-(
I tested this theory, by adding this new view, keeping the number
of views at 6 and the problem reoccurred on a different view
consistently. Updating views to 7 (the actual view count in the xml
file) and the problem went away. So when someone changes the view
node code to automatically count view nodes, this user-error will go
away. Until then, those of us that can't count will have to be
especially careful to make sure that the <number-views> is actually
set to the number of views in preferences.xml.
>> What about also increasing the number of views in the preferences
file,
>> if you add some?
>>
>> <number-views type="int">7</number-views>
>>
>> No idea, why we don't simply count the <view> nodes? Hmmm ...
>
>This is one of the older bits of code that did one of these arrays
of subsystem objects. I did it wrong >and never got back to fix it.
Counting and writing out the property would work fine. The only
changes >required would be within the init() in viewmgr.cxx. It'd be
a week anyway before I could get to it myself.
>
>Best,
>
>Jim
Thanks again for everyone's patience and to all that helped!
Ima
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
