JDK-8103267 : Report reasonable distances for parallel camera picking
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: scenegraph
  • Affected Version: 8
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2013-05-03
  • Updated: 2015-06-16
  • Resolved: 2013-10-30
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8Fixed
Related Reports
Blocks :  
JDK-8102438 - Specify parallel camera position in world
Sub Tasks
JDK-8103633 :  
Get rid of infinite intersected distance for parallel camera - Resolved
JDK-8103634 :  
Report correct distances for parallel camera based on its position - Resolved
Description
Parallel camera now renders everything regardless of the distance and the picking works the same way, reporting infinite distance for all points. Apparently parallel camera needs to have specific position in world with near/far clip planes working, so we should return correct distances.

We need to sort out whether to provide real distances to camera position (which would be natural) or the perpendicular distances to the camera plane (which may better correspond with the rendering).
Comments
Both subtasks are resolved, resolving also this parent issue.
30-10-2013
Looks like the above is agreed. I created two subtasks for the two steps outlined in the first comment.
14-05-2013
I prefer reporting the perpendicular distances of the point to the camera plane. This will correspond with rendering (objects with equivalent depth will have equivalent distance) and also will be straightforward to implement as distances are measured along pick rays that are perpendicular for parallel camera.
07-05-2013
Depends on knowing the camera position: RT-30188. Right now, to have the API right, we can at least remove the "infinity" from documentation and code and use a tentative camera position on [0, 0, -1], reporting negative distances for nodes behind camera until the other issues are solved.
03-05-2013