Align the `minAngleForTriangulation`, `minAngleForLandmark` and
`filterTrackForks` with the second SfM from the pipeline, and disable
the downscale in the DepthMap node.
Update the names of the commands that remove images in the "File"
menu to match with those in the Image Gallery menu.
"Clear Images" becomes "Remove All Images" and "Clear All Images" becomes
"Remove Images From All CameraInit Nodes".
Prior to this commit, the `StructureFromMotion` and `SfMTransform` nodes'
were directly set without using the dedicated command. This meant that
the actions to set those attributes through the Image Gallery menu were
not added to the stack of commands, and could not be undone.
In addition to the existing "Remove" menu action in the Image Gallery that
deletes the currently selected image, add a "Remove All Images" menu
action that performs the same action as "Clear Images" from the "File"
menu.
The "Del" key was used as a shortcut to remove the currently selected
image when the Image Gallery has the focus, "Shift+Del" can now also be
used to remove all the images at once.
Up to this commit, `meshroom_batch` only supported absolute input and
output paths: using relative ones led to a failure during the execution
of the `CameraInit` node.
Now, if relative paths are provided by the user, they are automatically
converted to absolute ones, thus ensuring that everything will run
smoothly.
The following parameters are updated:
- `minAngleForTriangulation` in the `SfMTriangulation` node for the
Camera Tracking and Camera Tracking Without Calibration templates
- `minAngleForLandmark` in the `SfMTriangulation` node for the Camera
Tracking and Camera Tracking Without Calibration templates
- `filterTrackForks` in the `StructureFromMotion` node for the Camera
Tracking, Camera Tracking Without Calibration and Photogrammetry and
Camera Tracking templates
Prior to this commit, when a `CameraInit` node was added to or removed
from the list of `CameraInit` nodes, the active `CameraInit` was always
reset to the first one in the list, independently from its previous
value.
This commit changes that behaviour by only modifying the active
`CameraInit` if no `CameraInit` node has been assigned yet, or if the
active `CameraInit` does not exist anymore (meaning it has been removed).
This requires to emit the `cameraInitChanged` signal every single time
the list of existing `CameraInit` nodes is modified even if the active one
is not changed, and to connect it to the ImageGallery in order to ensure
the index from the combo box always corresponds to the currently active
`CameraInit` node. Indeed, when the list of CameraInits is updated, the
model for the combo box is reset, and it needs to be re-updated with the
correct non-default value.
