Finally I'm getting down to the last of the planned changes in the view manager. The code should be submitted sometime today or this evening. There are some changes to the property structure that folks should be aware of, because they may affect custom configurations.
If you have any objection to these changes, now is the time to speak up :-) I think for the most part they won't cause any problems. A description of the changes effected from what is in CVS now follows. Best, Jim 1). New location for publishing "current" view's data. Formerly current offset values were published in various places in the /sim/view[0]/ branch regardless of which view they applied to. For example the pilot's eye offsets always appeared in /sim/view[0]/pilot. The chase view offsets where published in the /sim/view[1] branch and were coded as /heading/pitch/radius, while the viewer stored and used coordinates. Now all the active offsets for the current view will be published in "/sim/current-view/" in their correct type (angles or coordinates). These include: /sim/current-view/heading-offset-deg (formerly offset-deg) /sim/current-view/goal-heading-offset-deg /sim/current-view/pitch-offset-deg (formerly tilt-deg) /sim/current-view/goal-pitch-offset-deg /sim/current-view/axes/long /sim/current-view/axes/lat /sim/current-view/x-offset-m /sim/current-view/y-offset-m /sim/current-view/z-offset-m Note that at this time I won't be moving the FOV value, which appears in /sim/field-of-view. 2). New locations for configuration. The bindings in mice.xml will be modified to use the above described paths (heading-offset-deg/pitch-offset-deg). The bindings for keyboard.xml and joystick.xml will be modified to use the above listed paths (axes/long, axes/lat). The configuration for pilot eyepoint has changed in two ways (and will affect aircraft-set.xml files--probably just c172-3d-set.xml at this time). First of all the path for the offsets have been moved from /sim/view[0]/pilot to /sim/view[0]/config. Secondly I have reoriented the xyz offsets so that they are compatible with the rotation matrixes. The axis for x-offset-m now goes to the right, for y-offset-m goes forward, and z-offset-m goes up. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
