The raycaster can now pick lines... given a 3D precision threshold.
A ray can now compute its minimal distance to a segment

We can give optional targets to compute the points on the ray and the other on the segment (defining the minimal distance...)
A ray can now compute its minimal distance to a segment

We can give optional targets to compute the points on the ray and the other on the segment (defining the minimal distance...)
Merge branch 'dev' of https://github.com/stephomi/three.js into dev
Add test example with interactive lines.
Support for THREE.LinePieces raypicking.
Support for ray-line picking with scale matrix + polish few stuffs.
Add a simple test for ray-segment intersection.
Reverted to uint vased ids. Added uuid property.
Pheww... Glad that I figured this out in time.
Removed now unused defaultEulerOrder.
Sadly we can't add a setter/getter warning this time...
Removed setGeometry() and setMaterial() from Mesh. Moved the boundSphere check to Frustum and Raycasting.
Fixed example still using .setY()
Updated builds.