> Where the real time saving would come is if people write their code to use > InputDevices generically, so behaviours are not linked directly to mice > or Win98 device input. At least it'd save us a lot of time :-)
Have a look at the code for the Spaceball package which I submitted to the code repository of j3d.org . It does include several Inputdevices (using keyboard and/or mouse) - using the InputDevice interface - and a general Behavior which allows even change of the transformation (e.g. normal movement along axes and rotations or orbiting). Unfortunatly it is currently packaged in the repository under Spaceball which is a bit misleading. Probably this is what you are looking for. I was already wandering why the j3d chose to combine Behaviors and MouseInput directly insteaad of using the InputDevice interface which gives more flexibility. ( So if there is greater interest in using this system maybe Justin could change the packaging) regards Paul =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
