* If you reached this commit for a line in `git blame`,
re-run the blame operation starting at the parent of this commit
to see older history for the content.

(cherry picked from commit 86019e1878f613d59481f2b4d9aa02126ab2de41)

Add sliders for translations and rotation updates, linked to lidar proxies to help manipulate the sensor data

We want to be able to save the transform and other functionnality applied to a Lidar.

We tried to use "Save/Load paraview state" to save all the current open sources.
But there is a bug to load a ProxyProperty (transform) of a proxyProperty (Interpreter) of a proxy (Reader or stream).
The reapply of the transform does not work and may crash when we try to access it (https://gitlab.kitware.com/LidarView/lidarview-core/-/blob/master/ApplicationComponents/lqHelper.cxx#L256)

To restore a transform we add the "Save/Load Lidar State" button to each sensorsWidget in the sensor List.
It allows the user to save some properties of the specific Lidar into a json file
or to load the properties from a json file to a specific Lidar

The function updateProperty was very specific to the LoadLidarState function.
Everything was consider as string.
This function is moved to the only place it is used (the loadProperty reaction)

To update a property of a proxy, you should use the function vtkSMPropertyHelper(proxy, "propertyName").Set(value)
Then you should update the vtk Object using vtkSMProxy->UpdateProperty("propertyName") or vtkSMProxy->UpdateVTKObjects()

This will break the API of LidarView, to update it you have to :
- replace "UpdateProperty" by vtkSMPropertyHelper(proxy, "propertyName").Set(value)
- remove the cast into std::string
- add one of the 2 functions to update the vtkObject

MelanieCarriere authored 4 years ago and MelanieCarriere committed 4 years ago

This commit add some messages to the user :
- An instruction message
- If an empty json file is saved.
- If there is no property to display (if the json file loaded is empty for exemple)

MelanieCarriere authored 4 years ago and MelanieCarriere committed 4 years ago

The properties Start and Stop of the Stream are "vtkSMProperty".
Casting it into a proxy property raises a warnings that can be confusing for the user.

During loadLidarState function, the property was applied only if a proxy of the same name of the one saved was found in the pipeline.
For exemple :
If you save the LidarState with a LidarPacketInterpreter i1 and you open a file using a LidarPacketInterpreter i2
The properties saved from i1 couldn't be applied to i2.
This commit allows applying the property to a proxy of the same group.

If the property is not found in this proxy, the message is still display to the user.

MelanieCarriere authored 4 years ago and MelanieCarriere committed 4 years ago

With MSVC : a double[size] can not be instantiate with a non constant size.

MelanieCarriere authored 4 years ago and MelanieCarriere committed 4 years ago

The lidar state represents all the properties of a lidar source and ones of its subproxy (interpreter, ...)
A lidar source can be a lidarStream or a LidarReader.
This commit allow to save all or a part of theses properties in json file.
You can the reload them on a pipeline which already contains a lidar source