As far as I know sun's standard key navigation behavior uses
3 wakeup criteria keypressed, keyreleased and on elapsedframes(0)
and IMHO the elapsedframes(0) is responsible fo the cpu usage.
Take a look at David Nadeau's Course on Java3D
http://www.sdsc.edu/~nadeau/Courses/VR99/
in the examples there are excellent key navigation behaviors
( e.g .ExamineViewerBehavior) without wakeups on elapsedframes,
so your program will get the chance to do other things than
processing the key navigation behavior.
Happy hacking
Joerg
--
http://w5.cs.uni-sb.de/~baus
Email : [EMAIL PROTECTED]
Phone : +49-681-302-2016
Fax : +49-681-302-4136
===========================================================================
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".
