(cherry picked from commit 6d70de50)

Add sanity checks to avoid a crash while printing uninitialized objects.
All VTK classes should be printable right after the object is created.

fixes #17776

florian maurin authored 5 years ago and T.J. Corona committed 5 years ago

(cherry picked from commit 79f8a7d7)

florian maurin authored 5 years ago and T.J. Corona committed 5 years ago

(cherry picked from commit 92be4201)

Mathieu Westphal (Kitware) authored 5 years ago and T.J. Corona committed 5 years ago

(cherry picked from commit 4daf10b9)

Yohann Bearzi (Kitware) authored 5 years ago and T.J. Corona committed 5 years ago

This MR exposes ghosts at the vtkDataObject level.
Any subclass of vtkDataObject holding a data array
labelled as "vtkGhostType" can now be retreived
by calling vtkDataObject::GetGhostArray(int type),
where type is a vtkDataObject::AttributeTypes

(cherry picked from commit cf2ede9f)

florian maurin authored 5 years ago and T.J. Corona committed 5 years ago

(cherry picked from commit 79f8a7d7)
(cherry picked from commit 3447a9ca)

8.3 and 8.90 never actually saw a release.

vtkFieldData failed to call `this->Modified()` when array were removed.
This resulted in `vtkDataSet` maintaining an obsolete cache for ghost
arrays. Fixed that.

This class represents an interface for a UI
specific window. The intent is to pull the graphics
API apart from the basic window creation where possible.

At least one compiler complains about it being meaningless.

A first step to not requiring opengl and supporting
Vulkan/etc.

If this value is too small, the allocation of small data can result
in buffer exhaustion errors.

The method vtkPolyData::GetCellBounds() was no longer thread-safe
in certain conditions (vtkIdType not the same as the underlying
vtkCellArray storage type).