int Allocate(vtkIdType
->
vtkTypeBool Allocate(vtkIdType

int +(.*)::Allocate\(vtkIdType
->
vtkTypeBool \1::Allocate\(vtkIdType

GCC is getting smarter and detects that we're not copying the NUL
terminator over.

There are two approaches to fixing the warning:

  - where code is already a bit more complicated, just use `std::string`
    instead of C-style string manipulations; and
  - where we were doing `strncpy(dest, src, strlen(src))`, just use
    `strcpy` instead since the destination sizes are made based on the
    size of `src` anyways.

When the 2nd line of each timestep block contains a title, it is searched for a time keyword.
If not found, no timestep value was added to the list of timesteps, making it crash when setting
the TIME_STEPS() key

Significant rework of the hardware picking code.

Previously each mapper had to make sure that the rendered
colors were correct for point/cell etc ID during hardware picking
and this required large datastructures and texture uploads
to the GPU on each pick.

Now it collects the color buffers and gives the mappers a chance to
update them. This allows us to use gl_VertexId and gl_PrimitiveId
directly in the shader and then if picked, allow the mapper to
adjust the color buffer as needed. This allows us to avoid
rebuilding the VBO and textures each time and avoids the memory
footprint related to that.

 * introduce vtkMoleculeToLinesFilter
 ** Create polydata with atom == point, bond == line cell. Copy data.

 * Fix AtomBall and BondStick conversion:
 ** set array name for bond orders and atomic numbers
 ** fix allocated size

 * Introduce vtkAppendMolecule filter to append input molecules into one (with atomData and bondData)
 * Since vtkMolecule is in Common/DataModel, move vtkMoleculeAlgorithm to Common/ExecutionModel

Kitware Robot authored 6 years ago and Brad King committed 6 years ago

Populate a script with `map_<md5>=<sha512>` variable settings and
then run the following to convert the content link files:

    git ls-files -- '*.md5' | while read f; do
      md5="$(cat "$f")"
      sha512="$(eval echo \${map_$md5})"
      rm "$f"
      echo $sha512 > ${f%.md5}.sha512
    done

 * New filters:
   - vtkDistributedPointCloudFilter
   - vtkPointSetToMoleculeFilter
   - vtkPSimpleBondPerceiver
 * Improvement:
   - Add ghosts atoms in vtkMolecule and vtkMoleculeMapper
   - Use locator in vtkSimpleBondPerceiver
 * Fixes:
   - fix crash in vtkGraph
   - fix assert/crash in vtkPeriodicTable with out of range atomic number
 * Add relevant tests for new filters

154 occurances of ;;\n

This required some clean up, because the automatic changes borked a couple of files, but mostly resulted in stupid whitespacing. A few find/replace fixed things up.

There are now some duplicate semis because it did changes like:

  ~AMRIndexIterator() override{};
to
  ~AMRIndexIterator() override= default;;

Note there was a pointless semi before, which clang-tidy didn’t expect / account for.

My next commit will remove them.

found via `codespell` 

It seems like Mesa may use a half float rep when
it does not actually have float support. Or something
similar. So reduce the range of possible values to fit
within half float range.

The property isn't used anymore by the wrapping tools.

Now that Tcl wrapping is gone, all wrapping tools now use
`WRAP_EXCLUDE_PYTHON` instead.

Now that instantiators are gone, nothing cares about the ABSTRACT
property.

Now that VTK requires a C++11 compiler we can ditch using custom typedefs to
wrap =delete;

Now that VTK requires a C++11 compiler we can ditch using custom typedefs

Adding in functionality to allow inserting vtkNew objects into
stl containers of vtkSmartPointer objects as well as comparisons
between vtkNew objects and raw pointers. Also removing Get() and
GetPointer() calls from vtkNew objects since in most instances we
can just pass in the vtkNew<> object instead of having to use the
Get() or GetPointer() methods to get the raw pointer.

The old scalar material mode was largely unused or used in
an inappropriate manner and yet adds complexity and cost
to the code. Thsi topic removes it and replaces it with
an implementation that is similar to
VTK_MATERIALMODE_AMBIENT_AND_DIFFUSE so that scalar colors
are used for ambient and diffuse colors but the ambient
and diffuse intensities are still respected.

Previously scalar material mode when used
with scalars would ignore the ambient and diffuse
material intensities and when mapping one of them
set that one to 1.0 while leaving th eother alone.
This caused lots of odd situations where objects would be
over illuminated etc or where changing the diffuse or
ambient seemed to have o impact.

With this change the diffuse and ambient intensities
are always used. The sclaar simply controls the color
not the intensity.