David Megginson writes: > >Norman Vine writes: > > > Well the Mouse code certainly could but let's leave that alone > > as I REALLY don't want the Mouse reading properties :-) > >Not read them, but set them. It wouldn't much matter if the mouse >code called > > globals->get_current_view()->set_orientation_offsets(r, p, h); > >or > > view_roll_node->setDoubleValue(r); > view_pitch_node->setDoubleValue(p); > view_heading_node->setDoubleValue(h);>
Here is where I say you are WAY over enamoured with your 'properties' IMHO Since the properties can read/set a matrix directly all that is needed are these values stored in a 'globally available place' so that the property manager and its ilk can access them when they want to. But the internal vector math operators can operate unhindered by reading the values directly. What is really needed is a TOP DOWN evaluation of the program so that we can identify what needs to be exposed. Also I believe that all of the what was Viewer_RPH ie the World Positioning code without any 'eye' or other 'local orientations applied' should be moved out of FlightGear and into SimGear making this distinction even clearer. IMHO The same goes for the TileManager and Related Cache / Hitlist and a NON_FGFS specific TileEntry Class which FGFS can either use directly but I inmagine that these would be derived from for FGFS. Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
