I had similar problems, and my conclusion was that it performs a
"pickRandomly" type of function. So I moved back to the old PickObject API,
which at least seems to work. Has there been a bug report about this? I
didn't report it because I saw so many people in this group complaining
about picking that I thought this obvious one must have been covered...
-----Original Message-----
From: Discussion list for Java 3D API
[mailto:[EMAIL PROTECTED]]On Behalf Of Dvorak, Daniel J.
Sent: Monday, May 22, 2000 4:17 AM
To: [EMAIL PROTECTED]
Subject: [JAVA3D] New picking semantics in 1.2
After upgrading to 1.2 I got deprecation messages about my picking code, and
decided to change it to comply with the newest API. I used pickClosest
before, and since there's a method with the same name, expected it to work
the same way (i.e. - get a reference to the first node in the scene graph
intersected by the pick ray), like the documentation seems to state.
It seems that pickClosest actually sorts the intersected objects backwards,
meaning it is actually "pickFarthest". Can anyone verify? If so, is there
a workaround?
Daniel
===========================================================================
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".
===========================================================================
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".
