Resolve "GridItem can be moved without being shown"

Closes #297

See merge request !199

Resolve "Add possibility to edit chessboard properties to GUI"

Closes #176

See merge request !197

Resolve "Follow-up from "Resolve "Add more intrinsic calibration parameters"""

Closes #251

See merge request !160

Add Orcid to .zenodo.json file

See merge request !190

Update clang-format to 14.0.0

Closes #295

See merge request !196

ROI to full image and adjust to other ROI

Closes #271

See merge request !183

Resolve "Create `AutoSave` class and mechanism"

Closes #224

See merge request !154

Add AutoSave mechanism. The manual changes to the trajectories are counted. After 10 changes, the trajectories are exported to a hidden file. This hidden file can be loaded in the case of an crash of PeTrack. The project file is saved time based.

Hide analysis tab until it is fixed

Closes #280

See merge request !184

Update to OpenCV 4.5

Closes #126

See merge request !193

Fix loading saved sequence when opening a project

See merge request !192

Resolve "Move to frame by clicking on trajectory"

Closes #291

See merge request !188

Enables to move to a frame by clicking on a trajectory via Alt + Dbl-LClick

Add Orcid to .zenodo.json

See merge request !189

A hot fix for messed up intrinsic calibration files

Closes #145

See merge request !181

Delete obsolete code and comment to make `get3DPoint` more understandable

Closes #118

See merge request !187

- Add large comment describing the approach taken
- Use OpenCV data types when possible to do explicit matrix-vector-calculations

Add setting of marker ID to right click menu

Closes #289

See merge request !185

Merge trackingRoiItem and recognitionRoiItem in one class RoiItem

Closes #288

See merge request !182

Update video-compare script

See merge request !146

- frame-wise navigation when paused
- display frame number
- display diff and quality of displayed trajectories

Remove white border around exported pdf files

Closes #282

See merge request !180

Only reduce quality of tracked point on replacing detection

Closes #147

See merge request !174

We previously used a comparison to quality 100 for checking, if a point is a detection or not in the changed code. This was replaced by `80`, so a color-detection on e.g. a multicolormarker with code, which has quality 90, still gets counted as detection.

Also a helper function `isDetection` was created, so that this knowledge about the quality <-> detection relationship isn't scattered everywhere in the code.

Resolve "Merge doesn't delete already merged person from further evaluation"

Closes #274

See merge request !173

There was an error, where a person, who was already deleted because they were merged with another, still got evaluated. During this evaluation, the person which got the index of the deleted one got processed, or a segmentation fault happened, when the deleted person was the last one.

This is fixed by setting `mStatus` to not only signal not being tracked, but also, already being merged away.