-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Add the ability to set custom render window and renderer for pcl_visualizer #1989
Comments
Hi, before we can jump into the discussion, I would like to have a better understanding of the problem we are addressing:
|
http://pointclouds.org/documentation/tutorials/qt_visualizer.php
And crashes with debug message saying that the vtkGenericOpenGLRenderWindow is required, but vtkWin32OpenGLRenderWindow was received. I meant by 'new' that QVTKOpenGLWidget was added after qVTKWidget and requires Qt 5.4 |
What are the reasons to not use the "classical" |
QVTKOpenGLWidget is intended to be a replacement for QVTKWidget when using Qt 5, also it has features, that might be used in my project. Also, I have found better solution - make win_ and some other fields protected instead of private and implement new class based on PclVisualizer. |
Also, it will give us the ability to use the visualizer in VR with vtkExternalOpenGLRenderWindow |
Quick googling about
Additionally, I see this list of changes, with multiple bugfixes for With this in mind, keeping |
Ok, I will start working on it. |
Hi all.
I started working on it due to that pcl visualizer does not work correctly with new QVTKOpenGLWidget. It requires vtkGenericOpenGLRenderWindow.
I propose to add the constructor, that takes the smart pointers to render window and renderer and assigns them to internal pointers
PCLVisualizer(int &argc, char **argv, const std::string &name, vtkSmartPointer<vtkRenderWindow>& win, vtkSmartPointer<vtkRenderer>& renderer, PCLVisualizerInteractorStyle* style = PCLVisualizerInteractorStyle::New(), const bool create_interactor = true);
But there is small problem - in such signature we miss the default parameter for name. But i think the it will be not a problem for users to set it.
The text was updated successfully, but these errors were encountered: