You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the O3DVisualizer the current selection indicators points are massive if you load a point cloud which is scaled in e.g. mm:
In the "old" VisualizerWithEditing it looks fine, but I cannot use it as it crashes when trying to run it in a non-blocking way (see #1605 or #4378):
Smaller points are essential for robustly performing a manual N-point registration by point picking. So an UI element and API to adjust the point size would be appreciated. Also a smart default (like in the old visualizer) would be nice.
Further it would be helpful to be able to remove points after the fact, if one misclicked (again, like in the old visualizer).
References
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
) (#6733)
- Make points removable by correctly forwarding the key modifier to the already implemented function
- Fix bounding box calculation for picked point size selection (manual bbox extend calculation was wrong)
- Fix crash occurring when trying to make selection and non-pickable geometries where in scene
- Fix copy&paste error in help text for MACOS
Checklist
main
branch).Proposed new feature or change
In the O3DVisualizer the current selection indicators points are massive if you load a point cloud which is scaled in e.g. mm:
In the "old" VisualizerWithEditing it looks fine, but I cannot use it as it crashes when trying to run it in a non-blocking way (see #1605 or #4378):
Smaller points are essential for robustly performing a manual N-point registration by point picking. So an UI element and API to adjust the point size would be appreciated. Also a smart default (like in the old visualizer) would be nice.
Further it would be helpful to be able to remove points after the fact, if one misclicked (again, like in the old visualizer).
References
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: