Two small bugs for you: 1) Morph class requires weight to be around 1.0 in sum. I understand it is useful for debugging. Trick is that you can give negative ones, as long as sum is 1. This can lead to very interesting shapes :) It would make sense to either remove 1.0 sum requirement (and allow funny morphs like inversions etc), or check each value to be positive.
2) J3DTimer getValue() method return time in ticks, not in nanoseconds as it is described in javadoc (at least under windows). To get nanoseconds, you have to multiply times resolution. This is not bad, just out of sync with doc. So either, multiply it in J3DTimer, or change doc to stress that time is returned in resolution-ticks, not nanoseconds. Both bugs are absolutely non-critical, but I thought I'll let you know :) Artur =========================================================================== 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".
