[vtkusers] latest code that does not have the API change

[Mark Roden]

Ah, I see it:

CMake/advanced options/VTK_USE_QVTK_QTOPENGL

right?

On Mon, Apr 2, 2012 at 2:09 PM, Marcus D. Hanwell
<marcus.hanwell at kitware.com> wrote:
> Hi Mark,
>
> The class is not built by default, it is somewhat new but is in the
> release. It causes you to link to QtOpenGL and is added to QVTK if you
> activate the option. In VTK6 it is in its own module.
>
> Marcus
>
> On Mon, Apr 2, 2012 at 5:05 PM, Mark Roden <mmroden at gmail.com> wrote:
>> Hi Marcus,
>>
>> Thanks for the prompt reply.
>>
>> However, I also see that, for another project of mine, QVTKWidget2
>> does not appear to be in the 5.10.0-rc1.  Rather, it's there (in
>> \VTK\GUISupport\Qt), but it's not actually installed as part of the
>> installation project in Windows using the most recent CMake.  Is that
>> just a bug, or a difference between master and release (ie, is that
>> class not yet 'ready for primetime', and I'll need to update to master
>> to use it)?
>>
>> Thanks again,
>> Mark
>>
>>
>> On Mon, Apr 2, 2012 at 12:08 PM, Marcus D. Hanwell
>> <marcus.hanwell at kitware.com> wrote:
>>> On Mon, Apr 2, 2012 at 3:06 PM, Mark Roden <mmroden at gmail.com> wrote:
>>>> Hi all,
>>>>
>>>> I need to fix a bug in GDCM, and that code rests on top of VTK. GDCM
>>>> maintains backwards compatibility prior to VTK version 5, and setting
>>>> up all the possible build configurations will take time that I don't
>>>> have.
>>>>
>>>> If I sync to 5.10.rc1, will I be OK?  Is there a particular 'final'
>>>> tag I should look towards, before the API changeover?
>>>>
>>> The release branch would be a good place to base your work, that is
>>> before any API changes. Once it is released, the 5.10 tag would also
>>> work.
>>>
>>> Marcus