[vtkusers] Problem QVTKWidget using vtkCarbonRenderWindow instead of vtkCocoaRenderWindow

[Elvis Dowson]

Hi Mike,
                    I just finished trying out a vtk-5.3.x build with  
GUI support and QVTK support using Qt-4.5.x and I get the following  
errors:

Linking CXX shared library ../../bin/libQVTK.dylib
Undefined symbols:
   "vtkCarbonRenderWindow::UpdateGLRegion()", referenced from:
       QVTKWidget::DirtyRegionProcessor(OpaqueEventHandlerCallRef*,  
OpaqueEventRef*, void*)   in QVTKWidget.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[2]: *** [bin/libQVTK.5.3.0.dylib] Error 1
make[1]: *** [GUISupport/Qt/CMakeFiles/QVTK.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[100%] Building CXX object Geovis/CMakeFiles/vtkGeovis.dir/ 
vtkGlobeSource.o
[100%] Building CXX object Geovis/CMakeFiles/vtkGeovis.dir/ 
vtkGeovisInstantiator.o
Linking CXX shared library ../bin/libvtkGeovis.dylib
[100%] Built target vtkGeovis
make: *** [all] Error 2

It's purely related to QVTKWidget class and

a. vtk not being able to decide between using Carbon or Cocoa  
bindings, related to the absence of a pre-processor definition to help  
choose between the two
b. the QVTKWidget implement not being updated at the moment with calls  
to vtkCocoa methods. All the methods currently use only vtkCarbon  
methods

Shall I go ahead and modify the QVTKWidget sources? What is the  
procedure, do I make a change locally and then submit it to you guys  
to update the cvs repository?

Any ideas on which pre-processor symbol I can use to help switch  
between Carbon and Cocoa. At the moment, there is only one symbol  
Q_WS_MAC.

Best regards,

Elvis Dowson