[vtk-developers] Problem using VTK in a Cocoa application with the latest VTK (october 26th and later).

[Mathieu Coursolle]

TestInteractorTimers is one of those tests. However, it passes even if
the view is empty. I don't think it compares the window content, only
the timers result. 

I guess we could add an image compare to that test?

Mathieu

>I think we should add something similar to  SimpleCocoaVTK  as a test
>in Rendering/Testing, but not as an Xcode project example, it should
>work as any test, through a call to ctest.
>
>Even if we fix that now, it will prevent us from future breakage.
>
>On 10/30/07, David Cole <david.cole at kitware.com> wrote:
>> Is that a bug?
>> Yes.
>>
>> Would you recommend a particular fix...?
>>
>>
>>
>> On 10/30/07, Mathieu Coursolle < mcoursolle at rogue-research.com> wrote:
>> > Hi VTK developpers,
>> >
>> > I have been investigating a bit, and here is what I noticed.
>> >
>> > The way SimpleCocoaVTK is done right now calls
>> > vtkRenderWindowInteractor::Initialize() before it is
>> rendered
>> > the first time.
>> >
>> > At that point, CreateAWindow in vtkCocoaRenderWindow is called.
>> > It doesn't matter if the window is created of not. However, OpenGLInit()
>> > is called, which calls ReadOpenGLExtensions. That seems to required that
>> > the renderWindow been rendered once at that point (which is not the
case).
>> > If not, it calls render. However, render looks if OnScreenInitialized has
>> > been set to 1. It has not since we are still in CreateAWindow (it is set
>> > at the next line).
>> > Since it has not, it calls CreateAWindow again (which overwrites the one
>> > we are using)!
>> >
>> > Is that a bug?
>> >
>> > Thanks!
>> >
>> > MAthieu
>> >
>> >
>> >
>> ===========================================================
>> > Original mail
>> >
>> ===========================================================
>> >
>> > Hi VTK developpers,
>> >
>> > We developped a Cocoa application using VTK in an custom NSView.
>> > However, it stopped working since last Friday (october 26th).
>> >
>> > If we use october 25th build, it works all right, but our render
>> > window will not appear if we use a newer version. The code is based
>> > on SimpleCocoaVTK  (<
>> http://www.rogue-research.com/VTK/simpleCocoaVTK.html>),
>> > which has the same problem as we do if using the latest VTK (October
>> > 30th - 15h30).
>> >
>> > The vtkRenderWindow disappear at launch. In fact, you can see the render
>> > window for
>> > a really short period of time before it disappear.
>> >
>> > There is no VTK test which covers that issue (create the view for
>> > vtkRenderWindow), so the dashboard
>> > probably did not react to the changes. However, we have been using that
>> > code for
>> > the last months without any problem.
>> >
>> > Does anyone knows what is the cause of that problem. If so, is there a
>> > way to solve it?
>> >
>> > We are testing on Mac OSX 10.5.
>> >
>> > Thanks!
>> >
>> > --
>> >
>> ____________________________________________________________
>> > Mathieu Coursolle                   mcoursolle at rogue-research.com
>> > Rogue Research                      www.rogue-research.com
>> > Montréal, Québec, Canada
>> >
>> >
>> > _______________________________________________
>> > vtk-developers mailing list
>> > vtk-developers at vtk.org
>> > http://www.vtk.org/mailman/listinfo/vtk-developers
>> >
>>
>>
>> _______________________________________________
>> vtk-developers mailing list
>> vtk-developers at vtk.org
>> http://www.vtk.org/mailman/listinfo/vtk-developers
>>
>>
>
>
>-- 
>François Bertel, PhD  | Kitware Inc. Suite 204
>1 (518) 371 3971 x113 | 28 Corporate Drive
>                      | Clifton Park NY 12065, USA
>_______________________________________________
>vtk-developers mailing list
>vtk-developers at vtk.org
>http://www.vtk.org/mailman/listinfo/vtk-developers
>