My thoughts on this revolve around maybe coding the needed "triggers" into the viewer and then require each device to have a map of its controls to what the viewer is expecting.
we would need triggers for 1 Primary Secondary and Tetrary "buttons" 2 plus and minus translate for each of the X Y Z axis 3 plus and minus rotate for each of the X Y Z axis 4 some sort of toggle to swap from move to camera control Or am i just barking up the wrong tree?? and yes all of this should be in XML files so that we can update the list as needed -- Robert L Martin _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
