Add my voice to the praise for v.1.3. I've had a week now to explore setSchedulingInterval(), and I've been startled by its appetite for all of the procedural kluges that had infected my models. More and more things can be moved onto the scene graph where they belong. I can even see daylight in some places now.
Thanks, Java 3D Team. Just curious about the name, though. I suppose "scheduling interval" has some significance in the way that Behaviors are internally ordered, but to the user / scene builder, it's obfuscating. It's easy to hide, of course, so the comment doesn't qualify as a whine - after only a few times having to stop and figure out which way it worked, I covered it with a setPriority(), but the curiosity remains. Fred Klingener Brock Engineering =========================================================================== 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".
