Michael Selig <[EMAIL PROTECTED]> said:
> I have tried essentially what you mentioned. Here's specifically what I
> used in the uiuc-set.xml file:
>
> <view n="2">
> <config>
> <eye-heading-deg-path>/orientation/gamma-horiz-deg</eye-heading-deg-path>
> </config>
> </view>
>
> The outcome is that this gets ignored while the value in the
> preferences.xml file is used.
That's right, it doesn't. You are using the wrong view :-). The views are numbered starting with 0 (actually all properties are numbered that way). Like the example, <view n="1"> is the chase view.
Often I find the property browser very helpful for debugging these kinds of things. If your setting doesn't seem to work, go in there and take a look...often a minor misspelling, or misplacement becomes obvious.
Just the same, I will check to see if there isn't an issue there. It is possible that the viewer is initialized to the default path, that won't override, but we probably could make it change paths on the fly. My recollection though, is the model values get loaded before the view manager initializes, in which case it would work fine as is.
> > I think what would be really good is a feature where a user could load in > some customizations that override previously set values if they want. But > this view-angle thing does not require such a sweeping capability. >
Just about everything overrides the preferences.xml file. I haven't seen any problems in a long time.
OK! Very helpful. That did the trick ... using n=1 for view #2. Thanks.
Long ago I learned to count starting from 1 ... It's tough habit to break. Oh well, I got used to emacs, so I should be able to handle anything. ;)
Regards, Michael
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
