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.

If the user clicks in a plot that has an invalid (0,0) range, then in vtkContextScene::ProcessItem that is called after mouse events, the mapped mouse position becomes NaN, due to invalid matrix in the ContextScene's transform. This NaN position is then added to the function as a control point with an invalid NaN value. This fix makes sure this does not happen, by clamping the NaN values to minimum bounds on x axis, and 0 on y axis (any value comparison returns false if an operand is NaN, so need to check explicitly).

API improvement:

vtkAxis did not have an API to change minimum and maximum value
with one vtkChart::UpdateRange event.
This lead to inability to precisely shift an axis without temporarily
changing its range width (distance between minimum and maximum value),
and complexity and inefficiency when synchronizing axes
between multiple charts.

SetRange and SetUnscaledRange methods now invoke only one
vtkChart::UpdateRange event (after both minimum and maximum values
are updated).

Fixing minor issues:

1. Added a missing vtkCommand::InteractionEvent invocation
when vtkChartXY axes range are adjusted using ZoomAxis action
(this event indicates that the user adjusted axes and so the
application can propagate this change to other charts).

2. Fixed vtkChartXY transform computation logic

vtkChartXY unnecessarily recomputed transforms when axes
were modified after the chart's last modified timestamp.
ALso, vtkChartXY never recomputed transforms when chart
properties changed after axes changed, even when
recomputation would have been necessary.

Found via `codespell`

found via `codespell` 

includes grammar and uniformity fixes as well.

Found with regexes:

vtkBooleanMacro.*int\)
vtkBooleanMacro.*int \)

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

Commit 617ec438 introduced a regression caused by the assumption that
the XAxis and YAxis member variables are never null. This patch
handles the case where one or both of them are null.

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

The vtkControlPointItems now need XAxis and YAxis set.

Rather than 'fake' the log support in the context items, integrate
with the charting code and use the existing log scaling implementation.

This also fixes some issue with the charts log implementation.

Typos fixes for documentation and source code comments. This commit is a follow up to:   vtk/vtk!3424

- made vtkScalarsToColors::SetRange(double[2]) virtual, since the other SetRange() is.  Likewise vtkLookupTable::SetTableRange(double[2]).
- changed most uses of dangerous GetTableValue() (that returns inner buffer) in favour of version that copies the values out.
- use fixed-size memcpy in a few places for a potential speedup
- improved some comments
- added a few consts, especially with buffers
- removed const on plain old ints
- moved a nan check earlier, saving work when true
- moved some variable declarations closer to initialization
- removed some unneeded semi colons
- removed some useless casts, added others for clarity

vtkAbstractContextItem used to use unsigned int and converted -1 to unsigned int
This fixes it by using vtkIdType instead.

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.

This run of `clang-tidy` removes unnecessary `virtual` keywords and adds
`VTK_OVERRIDE` where necessary.

This fixes an issue with BadPoints hiding other points
Fix #17687

This redesign the algorithm so it is more consise
This also add a test and update a faulty baseline

These are defined elsewhere and do not need to be kept as comments.