Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide simple measure tool #1768

Open
dronus opened this issue Aug 11, 2016 · 6 comments

Comments

@dronus
Copy link

commented Aug 11, 2016

Please provide a simple tool where two vertex locations can be selected in the 3d view and their distance is shown.
This is especially useful as a quick check if the result of complex calculations matches the expectations.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@mon

This comment has been minimized.

Copy link

commented Jan 21, 2017

I've noticed resize works, and therefore must know object dimensions for x/y/z. Whilst not quite "pick two vertices" could it be worked into a size command that returns a 3 element dimension array for an object?

@kintel

This comment has been minimized.

Copy link
Member

commented Jan 21, 2017

resize() has to perform an implicit render(), which requires a round-trip into CGAL and may surprise the user with a huge performance penalty.
Due to this implicit rendering, we've been hesitant to add more functionality on top of resize or render, at least until we have a better way of making it clear that this is an expensive operation, or until we can replace the current CSG library with something significantly more performant.

However, there might exist opportunities for calculating world-space picked locations by performing CSG operations in one dimension along a ray cast through the design.

@MichaelAtOz

This comment has been minimized.

Copy link
Member

commented Jan 22, 2017

Would a 2D sizer be more efficient?
a. that would help with text(), which really is problematic not knowing the size.
b. could use projection to get the 2D bit you want (cut=true) or the max size on a plane (cut=false).

projection() is slow, is it (edit) CGAL (/edit) based?

@kintel

This comment has been minimized.

Copy link
Member

commented Jan 22, 2017

'projection' does few different things (CSG union, 2D union of all projected polygons), so it may be slow.

@donbright

This comment has been minimized.

Copy link
Member

commented Jan 25, 2017

projection was also slow because CGAL's projection was buggy and crashy and we had to do a bunch of bizarre workarounds. like projection into a really really thin box instead of projection into a plane. (not sure if that is still needed or if it even gets executed anymore since it tried to detect CGAL crashing before doing the workaround)

@kintel

This comment has been minimized.

Copy link
Member

commented Jan 25, 2017

In terms of projection stability, there is this issue: #1130

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.