- 28 Nov, 2017 1 commit
-
-
Jean-Loup Haberbusch authored
-
- 21 Nov, 2017 2 commits
-
-
Emmanuel Promayon authored
-
Emmanuel Promayon authored
set CAMITK_TEST_COVERAGE to TRUE to generate the 'camitk-test-coverage' target → it will create a coverage analysis report in ${PROJECT_BINARY_DIR}/camitk-test-coverage Update to latest additional CodeCoverage CMake modules by Lars Bilke (thanks to him!)
-
- 20 Nov, 2017 2 commits
-
-
Emmanuel Promayon authored
(sorry this has nothing to do with bug/activate-coverage...)
-
Emmanuel Promayon authored
see https://forge.imag.fr/plugins/mediawiki/wiki/camitk/index.php/Testcoverage for usage documentation
-
- 15 Nov, 2017 6 commits
-
-
Emmanuel Promayon authored
-
Emmanuel Promayon authored
-
Emmanuel Promayon authored
Fixed also: only one representation of vector and tensor is possible at a time.
-
Emmanuel Promayon authored
If a component inheriting from MeshComponent add data in the pointset before calling initRepresentation, they will be present in the data tab.
-
Emmanuel Promayon authored
Also clarified testdata vtk object name (colors are not yet implemented) and clean the MeshDataModel - MeshComponent interaction code
-
Emmanuel Promayon authored
-
- 14 Nov, 2017 5 commits
-
-
Emmanuel Promayon authored
-
Emmanuel Promayon authored
-
Emmanuel Promayon authored
The previous behaviour was a special case, but not really logical.
-
Emmanuel Promayon authored
-
Emmanuel Promayon authored
Now fully functionnal feature
-
- 13 Nov, 2017 1 commit
-
-
Emmanuel Promayon authored
-
- 10 Nov, 2017 1 commit
-
-
Emmanuel Promayon authored
Thanks go to Antoine for the nicer example.
-
- 09 Nov, 2017 5 commits
-
-
Emmanuel Promayon authored
Now 3D vector can also be displayed by their norm, or one the component magnitude.
-
Emmanuel Promayon authored
-
Emmanuel Promayon authored
see TODO for list of things to finish. This first test compiles but is not complete. The complete rewrite allows for a clear/real separation of data and GUI (as it should be)
-
Emmanuel Promayon authored
-
Emmanuel Promayon authored
-
- 08 Nov, 2017 3 commits
-
-
Emmanuel Promayon authored
Just need more redesign to make everything crystal clear, see TODO list
-
Emmanuel Promayon authored
Divide and conquer / easier to undestand / easier to maintain...
-
Emmanuel Promayon authored
-
- 07 Nov, 2017 13 commits
-
-
Emmanuel Promayon authored
-
Emmanuel Promayon authored
-
Emmanuel Promayon authored
At last vtkmesh contains only what it should...
-
Emmanuel Promayon authored
Action names should have space to be more user friendly...
-
Emmanuel Promayon authored
As the vtkmesh code was cleaned, this new tutorial was needed to show how to override pointPicked(..) and cellPicked(..) to manage mesh interaction.
-
Emmanuel Promayon authored
no need for this
-
Emmanuel Promayon authored
-
Emmanuel Promayon authored
initial/original point data are never removed, new demo data are added. Two type of generation: random (can be done as many times as you wish) and using the point index (only once) Note that the generated point data are automatically selected and visualize when the apply button is pressed.
-
Emmanuel Promayon authored
Note that point data were generated with the tutorial demo
-
Emmanuel Promayon authored
This means that all component that have GEOMETRY representation and contains no cell will be visible (automatic creation of a poly vertex cell containing all the points).
-
Emmanuel Promayon authored
-
Emmanuel Promayon authored
data are now displayed using the right scale
-
Emmanuel Promayon authored
-
- 06 Nov, 2017 1 commit
-
-
Emmanuel Promayon authored
-