View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0007226 | VTK | (No Category) | public | 2008-06-22 04:13 | 2016-08-12 09:54 | ||||
Reporter | Peter Wainwright | ||||||||
Assigned To | Kitware Robot | ||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||
Status | closed | Resolution | moved | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0007226: vtkRenderWindowInteractor does not work with Mesa | ||||||||
Description | I am trying to create and attach an interactor to a window using the VTK TCL shell. vtkRenderWindowInteractor iren iren SetRenderWindow renWin iren Initialize Specifically, I'm using the attached example from a tutorial I am working on a VNC display, and I have therefore had to put Mesa GL libraries in my LD_LIBRARY_PATH to emulate the GLX stuff. Unfortunately the interactor does not work; setting MESA_DEBUG=1 shows that there are errors in glXSwapBuffers: Mesa warning: glXSwapBuffers: invalid drawable 0x1600002 and the window does not redraw when the mouse is moved. This occurs with version 5.0.3-1ubuntu1 and with the CVS head. | ||||||||
Additional Information | What seems to be happening is this: Each buffer in Mesa's software GL is associated with a particular (display, drawable) pair. However, vtkXRenderWindowTclInteractor::Initialize() modifies the Display of the rendering window (so that it points to the first Display created by the Tcl shell). But the Mesa buffers were created in association with a different Display object. Although the 2 Display objects should be equivalent (they point to the same actual display device), Mesa does not like changing the Display here. | ||||||||
Tags | No tags attached. | ||||||||
Project | |||||||||
Type | |||||||||
Attached Files | vtktut6.tcl [^] (1,400 bytes) 2008-06-22 04:13 | ||||||||
Relationships | |
Relationships |
Notes | |
(0012971) Peter Wainwright (reporter) 2008-08-08 10:02 |
I notice that the problem does not occur if I remove the "renWin Render" calls, so that the window is not realized before the call "iren Initialize". This avoids the ambiguity of creating 2 Display objects which refer to the same physical display. The other way around it is to use a vtkTkRenderWidget instead. Again, there is only one Display object which is inherited from the initial toplevel Tk widget. |
(0036992) Kitware Robot (administrator) 2016-08-12 09:54 |
Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current VTK Issues page linked in the banner at the top of this page. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2008-06-22 04:13 | Peter Wainwright | New Issue | |
2008-06-22 04:13 | Peter Wainwright | File Added: vtktut6.tcl | |
2008-08-08 10:02 | Peter Wainwright | Note Added: 0012971 | |
2011-06-16 13:11 | Zack Galbreath | Category | => (No Category) |
2016-08-12 09:54 | Kitware Robot | Note Added: 0036992 | |
2016-08-12 09:54 | Kitware Robot | Status | expired => closed |
2016-08-12 09:54 | Kitware Robot | Resolution | open => moved |
2016-08-12 09:54 | Kitware Robot | Assigned To | => Kitware Robot |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |