[wxVTK] WindowRemap not implemented (was Re: Problems on Mac OS 10.5 and wxWidgets 2.8.7)

[Mathieu M. <mat...@gm...>]

Hi Doug,

  Alright finally some progress ! Don't forget to send me the patch in
the end :)

On Fri, Aug 15, 2008 at 12:04 AM, Doug McCorkle <mc...@ia...> wrote:
> I got everything built now. I just told cmake to use the 10.5 sdk not the
> 10.4. Anyway, I now get this when running a sample:
>
> leonidas:build mccdo$
> ./wxImagePlaneWidget.app/Contents/MacOS/wxImagePlaneWidget
> ERROR: In /Volumes/data/VE_Suite_Deps/VTK_new/VTK/IO/vtkVolume16Reader.cxx,
> line 355
> vtkVolume16Reader (0x3571a00): Can't find file:
> ../../../../VTKData/Data/headsq/quarter.1

I do not think I implemented the -D command line option, so you have to do:

  export VTK_DATA_ROOT=/Volumes/data/VE_Suite_Deps/VTK_new/VTKData

  If you do not have VTKData, download it from the vtk.org page (you
can do it from CVS command line by replace VTK with VTKData)


> Warning: In
> /Volumes/data/VE_Suite_Deps/VTK_new/VTK/Rendering/vtkCocoaRenderWindow.h,
> line 138
> vtkCocoaRenderWindow (0x35716c0): SetNextWindowId not implemented
> (WindowRemap not implemented).

ouch !

> Warning: In
> /Volumes/data/VE_Suite_Deps/VTK_new/VTK/Rendering/vtkCocoaRenderWindow.mm,
> line 813
> vtkCocoaRenderWindow (0x35716c0): Can't remap the window.

ouch 2 !

> 2008-08-14 17:01:02.903 wxImagePlaneWidget[47823:10b] invalid drawable
> 2008-08-14 17:01:02.938 wxImagePlaneWidget[47823:10b] invalid drawable
> ERROR: In
> /Volumes/data/VE_Suite_Deps/VTK_new/VTK/Rendering/vtkInteractorStyle.cxx,
> line 392
> vtkInteractorStyleJoystickCamera (0x3567600): Timer start failed

I think David Cole fixed this 2 year old bug yesterday. One way to
know would be to update your copy of VTK and rebuild. If you are using
VTK 5.2 the patch will be merged in a couple of day.

<...>

> And I see two windows which does not seem correct.

Alright so this leave us with one issue the WindowRemap not
implemented for Cocoa. But technically this is not required. So I am
not sure how this is happening.

If you add let say an 'abort()' call on line 742:

      //this means the user has reparented us; let's adapt to the
      abort();

If you recompile+rerun, if you hit this abort, this is bad news, it
means the wxVTK did not work as expected. The way it was designed is
that the function GetHandleHack() cannot be called too early, but only
after the first OnPaint event. Check wxVTK::OnPaint and print the
value of Handle at the end of the function.

As usual send me the output.

-- 
Mathieu