[vtkusers] VTK and GUI - vtkRenderWindow - Virtual or Physical?

[Andrew J. Dolgert]

Your idea is interesting. It might apply to attempts to use VTK as a
server for AJAX. For Windows Forms, however, the current setup works
fine because the vtkWin32OpenGLRenderWindow will happily receive events
from and draw into the Frame of a Windows Form because Windows Forms
expose their HWND handle.

 

Drew Dolgert

 

________________________________

From: vtkusers-bounces+ajd27=cornell.edu at vtk.org
[mailto:vtkusers-bounces+ajd27=cornell.edu at vtk.org] On Behalf Of Frank
Gao
Sent: Friday, March 17, 2006 5:24 PM
To: Vtkusers at Vtk.Org
Subject: [vtkusers] VTK and GUI - vtkRenderWindow - Virtual or Physical?

 

Hi Experts,

 

I have a question about vtkRenderWindow, and vtkOpenGLRenderWindow. Are
such objects virtual, or have to be physical by setting the parent
window ID? 

 

The requirement behind this question is here. Suppose an application
must separate its window display and interaction from its internal code.
The application needs to set a virtual vtkOpenGLRenderWindow with
interactors that are also virtual, and binding them with a physical
window whenever necessary. Simply put, make vtkOpenGLRenderWindow and
the interactor purely 'server' objects to return bitmaps (or video
streams?). These server objects are fully functional and independent of
physical implementation. By doing this, the application never needs to
get into vtk code to change files such as vtkMFCWindow. 

 

A real scenario for this. If this is possible, with a .Net wrapper, one
can easily use Win Forms as render window.

 

It would be tremendously helpful if the answer is YES, or can be YES.
Your replies are highly appreciated.

 

Thanks,

 

Frank Gao

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20060318/c004dc74/attachment.htm>