# Yet another QVTKOpenGLWidget renaming ?
**URL:** https://discourse.vtk.org/t/yet-another-qvtkopenglwidget-renaming/2602
**Category:** Development
**Created:** [February 13, 2020, 7:26am UTC](https://discourse.vtk.org/t/yet-another-qvtkopenglwidget-renaming/2602 "2020-02-13T07:26:21Z")
**Posts on this page:** 6
**Page:** 2
### Author:  [@mwestphal](https://discourse.vtk.org/u/mwestphal)
#### Post date: [February 18, 2020, 3:06am UTC](https://discourse.vtk.org/t/yet-another-qvtkopenglwidget-renaming/2602/21 "2020-02-18T03:06:21Z")
I agree. So let’s poll again :
_Poll ([view on site](https://discourse.vtk.org/t/yet-another-qvtkopenglwidget-renaming/2602/21))_
please refrain to post until this poll is closed in two or three days.
---
### Author:  [@mwestphal](https://discourse.vtk.org/u/mwestphal)
#### Post date: [February 20, 2020, 3:40am UTC](https://discourse.vtk.org/t/yet-another-qvtkopenglwidget-renaming/2602/22 "2020-02-20T03:40:08Z")
Looks like it is quite even.
After discussing with @cory.quammen, I think the best would be to :
- Go forward with a low level rename of the widgets.
- Add a simple high-level named wrapper ready to be expanded once vulkan or other implementation are integrated and that can be used by applications, which points, for now, to QVTKOpenGLNativeWidget.
The only low-level rename proposition was then :
```
QVTKOpenGLNativeWidget -> QVTKOpenGLNativeWidget (no rename)
QVTKOpenGLWidget -> QVTKOpenGLStereoWidget
```
Let me know if there is a strong opposition to this suggestion.
---
### Author:  [@borisb](https://discourse.vtk.org/u/borisb)
#### Post date: [February 20, 2020, 9:40am UTC](https://discourse.vtk.org/t/yet-another-qvtkopenglwidget-renaming/2602/23 "2020-02-20T09:40:25Z")
> [@mwestphal](#):
>
> As some have remarked it, this suggest the the newly named QVTKOpenGLStereoWidget will never be adopted as a generic widget. I personally am fine with that. So difficulties present with it are inherent to it’s design and can’t be solved on our side, but only on Qt/GraphicDriverStack which we have no control of. As this design is not preferred by the Qt community, I’m not hopeful for these issues to be fixed.
It should also be noted that QVTKOpenGLNativeWidget has an issue when enabling multisampling, see [https://gitlab.kitware.com/vtk/vtk/issues/17154](https://gitlab.kitware.com/vtk/vtk/issues/17154). The problem seems to come from Qt as understood by @utkarshayachit ([https://gitlab.kitware.com/vtk/vtk/issues/17154#note\_546700](https://gitlab.kitware.com/vtk/vtk/issues/17154#note_546700)). Because of this, I’m using mostly QVTKOpenGLWidget in my own applications, which does not suffer from this issue. So personally, I’m not particularly in favor of renaming this widget by adding a “Stereo” label to it, since I don’t use QVTKOpenGLWidget for its stereo capabilities at all. But I agree that for the other widget, the “Native” term is not very clear.
---
### Author:  [@mwestphal](https://discourse.vtk.org/u/mwestphal)
#### Post date: [February 25, 2020, 9:49am UTC](https://discourse.vtk.org/t/yet-another-qvtkopenglwidget-renaming/2602/24 "2020-02-25T09:49:45Z")
Here it is : [https://gitlab.kitware.com/vtk/vtk/merge\_requests/6506](https://gitlab.kitware.com/vtk/vtk/merge_requests/6506)
---
### Author:  [@mwestphal](https://discourse.vtk.org/u/mwestphal)
#### Post date: [March 3, 2020, 3:41am UTC](https://discourse.vtk.org/t/yet-another-qvtkopenglwidget-renaming/2602/25 "2020-03-03T03:41:23Z")
The MR has been merged.
---
### Author:  [@mwestphal](https://discourse.vtk.org/u/mwestphal)
#### Post date: [December 13, 2023, 10:17am UTC](https://discourse.vtk.org/t/yet-another-qvtkopenglwidget-renaming/2602/26 "2023-12-13T10:17:56Z")
A post was split to a new topic: [QOpenGLWidget question](https://discourse.vtk.org/t/qopenglwidget-question/12895)
[Previous page](https://discourse.vtk.org/t/yet-another-qvtkopenglwidget-renaming/2602.md?page=1)