-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
non-blocking VisualizerWithEditing #1605
Comments
Hi @markkorput, We are working on a new version of the Visualizer. I will add a non-blocking version of an editing tool to our roadmap. |
Is there any new progress regarding this feature? |
The new visualizer is available in 0.12, it is We are working on a better way of running O3DVisualizer non-blocking, but for now there are two approaches. One is illustrated in
This way is simpler, but the GUI won't process events like mouse events outside of |
Hi, can you add a tutorial of the non-blocking interactive visualizer? I currently have a non-blocking visualizer working and want to make it interactive without overhauling it completely. Any suggestions? |
Is your feature request related to a problem? Please describe.
It would be great to be able to pick points from a pointcloud (and perform other operations), without blocking your application. When I use VisualizerWithEditing and try to run it non-blocking mode (see code below), it crashes as soon as I pick a point using shift+click (see log below).
Describe the solution you'd like
It would be great to have a fully functional non-blocking
VisualizerWithEditing
.Describe alternatives you've considered
I considered using the 'normal' blocking version of VisualizerWithEditing in a separate thread, but since it would still be blocking on the separate thread, there would be no way to update geometry when things in other parts of the application change, or close the Visualizer when needed.
Additional context
current code
crash log
[Open3D INFO] Picked point #142192 (1, 0.18, 3.4) to add in queue. Segmentation fault: 11
The text was updated successfully, but these errors were encountered: