[vtk-developers] vtkCocoaRenderWindow qq
Sean McBride
sean at rogue-research.com
Thu Oct 2 11:20:03 EDT 2008
On 10/2/08 10:37 AM, Francois Bertel said:
>Are talking about changing the vtkCocoaRenderWindow only or the
>superclasses as well?
Only vtkCocoaRenderWindow.
>If it is only the vtkCocoaRenderWindow, it does not sound like a big
>deal to me.
>
>The mechanism is to keep the existing methods and mark them as
>obsolete with some macros defined in VTK/Common/vtkSetGet.h
>
>An example of this is VTK/Filtering/vtkViewport.h/cxx:
>
>AddProp() has been deprecated in favor of a new AddViewProp (to avoid
>conflict with some Windows macros)
>
>vtkViewport.h:
>
>// Description:
> // @deprecated Replaced by vtkViewport::AddViewProp() as of VTK 5.0.
> VTK_LEGACY(void AddProp(vtkProp *));
>
>
>vtkViewport.cxx:
>
>#ifndef VTK_LEGACY_REMOVE
> void vtkViewport::AddProp(vtkProp* p)
>{
> VTK_LEGACY_REPLACED_BODY(vtkViewport::AddProp, "VTK 5.0",
> vtkViewport::AddViewProp);
> this->AddViewProp(p);
>}
>#endif
The situation is a little different though. In this case, Clinton is
talking about 4 get/set method pairs in vtkCocoaRenderWindow that are
all from vtkWindow. These 4 method pairs would remain, but their
behaviour would change. No methods would be added or removed or
renamed. Foo() will do what Bar() did, and Bar will do what Foo() did, etc.
--
____________________________________________________________
Sean McBride, B. Eng sean at rogue-research.com
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
More information about the vtk-developers
mailing list