CamiTK Community Edition issueshttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues2024-02-23T11:20:59+01:00https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/180Simplify CamiTKVersion.h management2024-02-23T11:20:59+01:00Emmanuel PromayonSimplify CamiTKVersion.h management| | |
|--|--|
| **As a** | CamiTK developer and packager |
| **I would like to** | simplify the release and packaging process |
| **So that** | it would be easier to publish and package a new version |
| **Epic/Topics** | release managem...| | |
|--|--|
| **As a** | CamiTK developer and packager |
| **I would like to** | simplify the release and packaging process |
| **So that** | it would be easier to publish and package a new version |
| **Epic/Topics** | release management |
## Description / Overview
This point for this issue is:
- gather explanation about/rationale behind the existence of `CamiTKVersion.h` and `CamiTKVersion.h.in` file
- explain some consequence of the existence of this file
- work on how it can be simplified
## Hints
`CamiTKVersion.h` contains static information about the version number, debug postfix and `libDir`.
This file generates some complicated maneuvers during release management and packaging (see below).
### Some background on plugins
- CamiTK has a core library and uses plugins to add I/O (components), processing (actions) and viewer functionalities
- the plugins are made available using .so stored in "camitk repository", a directory that has a specific structure with subdirectories to sort plugins depending on their nature (actions, components, viewers)
- at run time, the core library looks into different paths for locating the existing camitk repositories (working directory, user installed, locally installed, or globally installed) in order to dynamically load all the available plugins.
- The libDir variable is used to check the camitk repository paths, that should all be ending with "some/path/" + libDir + "/camitk-x.y" (where x.y are major.minor camitk version numbers).
- The CamiTKVersion.h header file is used to specify this statically.
- On the upstream develop branch, libDir is generated at configure time by CMake, using the CMAKE_INSTALL_LIBDIR variable which is either set to "lib/ARCH" (if CMAKE_INSTALL_PATH is set to "/usr") or to just "lib/" (if CMAKE_INSTALL_PATH is empty).
- on the upstream master branch (the stable version, used to generate the tar ball), this is fixed to "lib". **TODO: describe rationale behind this**
### Generated burden
It might not be the best way to proceed, it is a bit complicated... That's what we came up with at the time (pre 2011) to answer to the following support constraints :
- multiple os,
- multiple camitk repositories,
- and multiple build situation (inbuild, sdk, install, cep dev)
It looks more like technical debt and could probably be simplified as it impact
- the release management process
- the packaging process (s.g. during 5.2 release `CamiTKVersion.h` was different on debian salsa master and in the upstream tarball), see also d/r and the line that uses `sed` to correct the file on debian...
### Note on `libDir` introduction in CamiTK version
`libDir` in CamiTKVersion was introduced #109 and #117 (commit de1794622009c4edd6cf4220773b61dbd644c37e) in order to support gentoo, and was later modified to take into account more situations:
- lib (default)
- lib64 (used on some Linux/platform)
- lib/<multiarch-tuple> (on Debian)
### Fixing this issue
Fixing this issue can be done either by
- option 1: confirming that a static `CamiTKVersion.h` (part of all of it) is required in `master`
- option 2: removing `CamiTKVersion.h` in master and generated release version tarball
## Acceptance tests
- [ ] option 1: better documentation to explain why a static `CamiTKVersion.h` is required
- [ ] option 2: a branch fixing this issue is merged (therefore CI passed)
- [ ] option 2: successful debian packaging process test
## Track
## Misc
- Automatic subscription of issue creator:https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/179Persistence: select parts to save, support Action properties, automatic actio...2024-03-26T19:15:48+01:00Manik BhattacharjeePersistence: select parts to save, support Action properties, automatic action replay and processing scenarios in camitk files## About you
CamiTK developer
## Product
PersistenceManager and Actions
## Overview
- PersistenceManager should allow to select which parts to save in saveWorkspace, maybe with flags (components/actions/history/mainwindow/viewers...)...## About you
CamiTK developer
## Product
PersistenceManager and Actions
## Overview
- PersistenceManager should allow to select which parts to save in saveWorkspace, maybe with flags (components/actions/history/mainwindow/viewers...)
- Action properties should be loaded without causing a crash: add a flag to Action to say whether they support parameter reloading
- Actions should specify (with a flag) whether they should be replayed (e.g. Mesh Projection: when the workspace is loaded, we want to show again the mesh projections, SmoothingFilter should be re-applied to show smooth meshes)
- Processing scenarios and History support should be added in CamiTK files and saveWorkspace, with a corresponding load function.
- Add an "Export Workspace" that saves the workspace in a directory and "save as" all components in this directory. This avoids the problem of unsaved components when saving a workspace (e.g. with CEP Focus, ultrasound acquisitions can produce many volume images, and the user wants to save everything without entering a filename for each component, so exporting the whole workspace, components included would be useful)
---
**please do not remove anything below this line**Manik BhattacharjeeManik Bhattacharjeehttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/178Pick a point in 3D Viewer, view a 3D cursor2024-01-31T18:55:06+01:00Manik BhattacharjeePick a point in 3D Viewer, view a 3D cursor## About you
CamiTK developer, from multiple users' wishlist.
## Product
Medical Image Viewer, 3D Viewer
## Overview
Currently, the user cannot ctrl+click on a point in the 3D Viewer (except to select a part of a Mesh), and the curre...## About you
CamiTK developer, from multiple users' wishlist.
## Product
Medical Image Viewer, 3D Viewer
## Overview
Currently, the user cannot ctrl+click on a point in the 3D Viewer (except to select a part of a Mesh), and the currently selected point is not visible in the 3D View.
- The users would like to be able to click on an ImageComponent to set the coordinates of a point, like when using Ctrl+Click on 2D Views.
- This should also work on a MeshComponent.
- Showing the position of this point as a 3D cursor (such as a 3D cross) would be a plus.
- Clicking on an Actor could also be used to select components (e.g. clicking on a mesh should select the associated mesh component)
---
**please do not remove anything below this line**https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/170Elastix registration using the elastix command2023-11-26T18:34:59+01:00Emmanuel PromayonElastix registration using the elastix command| | |
|--|--|
| **As a** | camitk-imp user... |
| **I would like to** | register image using the elastix software from CamiTK |
| **So that** | I can change the main parameter, call elastix and see the registration result in CamiTK witho...| | |
|--|--|
| **As a** | camitk-imp user... |
| **I would like to** | register image using the elastix software from CamiTK |
| **So that** | I can change the main parameter, call elastix and see the registration result in CamiTK without using the command line |
| **Epic/Topics** | medical image registration |
## Description / Overview
Select main registration parameters in an Action interface. Apply registration using "Apply" button
Basically this issue is to perform [MISR tutorial 3](https://promayoe.gricad-pages.univ-grenoble-alpes.fr/walnut/tutorials/misr/03/index.html) using camitk-imp instead of the command line.
## Hints
Call elastix/elastix.exe from the action
## TrackEmmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/169add dbus connection2023-10-29T13:49:12+01:00Emmanuel Promayonadd dbus connection## About you
CamiTK dev
## Product
CamiTK Core / Application
## Overview
Issue #168 was not detected during configure/make/test as it is not possible to set a test where an application that starts a user interaction loop would be ru...## About you
CamiTK dev
## Product
CamiTK Core / Application
## Overview
Issue #168 was not detected during configure/make/test as it is not possible to set a test where an application that starts a user interaction loop would be run and stopped automatically after a while. For example, in the case of `camitk-fancy` that would have allowed for a simple start and exit. In the presence of a bug similar to #168, the test would then have failed.
A possible way of offering extended testing for application would be to add the possibility for any CamiTK application to listen to dbus messages.
- it would then be possible to send message from outside the application (e.g. a shell, a test script or program...) such as "run action `Quit`".
- it would also add the **great** advantage of opening a whole lot of testing and automation. For instance by sending message analog to state in the action state machine (e.g. by sending XML/json message containing the action to apply and its parameter).
## Relevant logs and/or screenshots
### Adding dbus message support in CamiTK::Application
For instance by using:
```cpp
QDBusConnection::sessionBus().connect(QString(), QString(), "camitk.action", "apply", this, SLOT(applyActionFromDBus(QString)));
...
void Application::applyActionFromDBus(const QString &message) {
if(message=="...") {
...
}
}
```
### From the test application
```cpp
QProcess myProcess;
myProcess.start("camitk-fancy", "");
if (!myProcess.waitForStarted())
return false;
QDBusMessage msg = QDBusMessage::createSignal("/", "camitk.action", "apply");
message="Quit"
QDBusConnection::sessionBus().send(msg);
if (!myProcess.waitForFinished())
return false;
```
**Note**
DBus is supported on Linux desktops by default. A [windows port exists](https://www.freedesktop.org/wiki/Software/dbus/#download) but this need further checks.
### dbus not allowed by default
For security reason, the default behaviour should be _not_ to listen to DBus, and flag `--dbus` should be added to the arguments to enable the feature in the application.
### See also
[KDE doc for creating dbus interface](https://develop.kde.org/docs/features/d-bus/creating_dbus_interfaces/)
---https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/167ITK Registration Action2023-10-26T16:58:56+02:00Celine FouardITK Registration Action| | |
|--|--|
| **As a** | CamiTK User / Student |
| **I would like to** | Use basic registration technics to align 2 images |
| **So that** | I could visualize registration results directly on CamiTK |
| **Epic/Topics** | Integrate ITK ...| | |
|--|--|
| **As a** | CamiTK User / Student |
| **I would like to** | Use basic registration technics to align 2 images |
| **So that** | I could visualize registration results directly on CamiTK |
| **Epic/Topics** | Integrate ITK Registration into CamiTK |
## Description / Overview
Select mandatory registration parameters on an Action interface. Apply registration
## Acceptance tests
[Please enter acceptance tests as TODOs. Acceptance test explains how to test that this issue is solved]
- [ ] [Test 1]
- [ ] [Test 2]
- [ ] [...]
## Track
[Please keep only one of the following label]
## Misc
- Automatic subscription of issue creator:
**If appropriate, do not forget to mark this issue as "confidential"** by checking the corresponding tick box belowCeline FouardCeline Fouardhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/166Python bindings: Python CEP and scripting2023-10-13T18:11:11+02:00Manik BhattacharjeePython bindings: Python CEP and scripting## About you
CamiTK developers
## Product
CamiTK
## Overview
Allow Python CEP and Python scripting
---
**please do not remove anything below this line**## About you
CamiTK developers
## Product
CamiTK
## Overview
Allow Python CEP and Python scripting
---
**please do not remove anything below this line**Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/142Toolbar for each viewer2023-06-14T08:19:10+02:00Manik BhattacharjeeToolbar for each viewer## About you
CamiTK developer
## Product
IMP UI and Viewers
## Overview
The main toolbar does not apply to all viewers, which is confusing, and does not allow buttons specific to a viewer (e.g. display mode).
Code structure is alread...## About you
CamiTK developer
## Product
IMP UI and Viewers
## Overview
The main toolbar does not apply to all viewers, which is confusing, and does not allow buttons specific to a viewer (e.g. display mode).
Code structure is already developed with viewer-specific toolbars in mind.
---
**please do not remove anything below this line**Manik BhattacharjeeManik Bhattacharjeehttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/141Add icon next to components to show/hide components in viewers2023-11-24T19:10:15+01:00Manik BhattacharjeeAdd icon next to components to show/hide components in viewers## About you
CamiTK developer
## Product
Main IMP interface - Component explorer
## Overview
In the list of components in camitk-imp, it would be useful to have an eye icon next to the component's name to click on to show or hide co...## About you
CamiTK developer
## Product
Main IMP interface - Component explorer
## Overview
In the list of components in camitk-imp, it would be useful to have an eye icon next to the component's name to click on to show or hide components in views.
As visibility depends on the view:
- should we add a ViewerExplorer in IMP that would allow to select views (adding or removing components from views before setting visibility,
- just show/hide on all views ?
- Allow drag and drop of a component into a viewer to make it visible in that viewer.
## Relevant logs and/or screenshots
Eye icons that are already present in CamiTK: sdk/libraries/core/resources/oxygen_icons/actions/layer-visible-on.png
---
**please do not remove anything below this line**Manik BhattacharjeeManik Bhattacharjeehttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/140Better LUT editor, standard LUT should be provided as well2024-03-25T17:37:38+01:00Manik BhattacharjeeBetter LUT editor, standard LUT should be provided as well## About you
CamiTK developer
## Product
sdk/actions/image/imagelut
## Overview
The LUT editor only allows to choose one color (changing the first color does nothing) and go from black to that color.
There is no way to create a LUT t...## About you
CamiTK developer
## Product
sdk/actions/image/imagelut
## Overview
The LUT editor only allows to choose one color (changing the first color does nothing) and go from black to that color.
There is no way to create a LUT that goes from blue to yellow to red for example, and that should be possible.
We should also provide a list of "standard" LUTs, maybe taken from another opensource project (Brainvisa/Anatomist ?).
The same editor could be used for the 3D rendering widget as well if we can also set transparency (RGBA) of the reference values
Saving a user's custom LUTs would be useful too.
To avoid the UI being too complex,
- use one tab to select a palette and set window level and width (adapted to the range of the image type - e.g. 0-65535 for uint16 or -2B/+2B for int32, not 0-255 in all cases)
- use another tab to create a new palette
## Relevant logs and/or screenshots
BrainVisa/Anatomist palette system: https://brainvisa.info/anatomist-5.0/user_doc/anatomist_tutorial.html#modification-of-color-palette
---
**please do not remove anything below this line**Manik BhattacharjeeManik Bhattacharjeehttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/139CamiTK does not read OBJ material file2023-06-05T17:22:36+02:00Manik BhattacharjeeCamiTK does not read OBJ material file## About you
CamiTK developer
## Product
sdk/obj/ObjComponent
## Overview
The OBJ file format can be associated with a .mtl file that store the material (RGBA color). This is ignored by CamiTK.
## Relevant logs and/or screenshots
V...## About you
CamiTK developer
## Product
sdk/obj/ObjComponent
## Overview
The OBJ file format can be associated with a .mtl file that store the material (RGBA color). This is ignored by CamiTK.
## Relevant logs and/or screenshots
VTK has two objects to read obj files: CamiTK should use VtkObjImporter (and not VtkObjReader) and use its support for mtl files.
A test object can be easily generated in Blender (standard cube + material exported as obj file).
---
**please do not remove anything below this line**Manik BhattacharjeeManik Bhattacharjeehttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/138Add support for RGBA color2023-06-05T17:16:25+02:00Manik BhattacharjeeAdd support for RGBA color## About you
CamiTK developer
## Product
MeshComponent
## Overview
MeshComponent can have associated data. If the display mode is COLOR, the data is read as RGB data.
If there is a 4th dimension (A for alpha transparency), this is no...## About you
CamiTK developer
## Product
MeshComponent
## Overview
MeshComponent can have associated data. If the display mode is COLOR, the data is read as RGB data.
If there is a 4th dimension (A for alpha transparency), this is not supported.
It should be checked whether data works if it is encoded as:
- double/float between 0 and 1,
- int 8/16/32 bits in their respective range
## Relevant logs and/or screenshots
Check commit d827e23daf036652c10657bd57f12d0819ba0891
In libraries/core/mesh/MeshComponent.cpp
`colorArrayToDisplay->SetTuple3(i, val[0], val[1], val[2]);`
should work when there are 4 values with setTuple4. Hopefully VTK would use that as RGBA.
---
**please do not remove anything below this line**Manik BhattacharjeeManik Bhattacharjeehttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/132Option to highlight selected object by silhouette2023-04-21T19:56:41+02:00Manik BhattacharjeeOption to highlight selected object by silhouette## About you
CamiTK developer
## Product
Core in InteractiveViewer.
## Overview
In the main viewer, unselected elements are transparent, selected elements are not.
Add an option to show unselected elements as non-transparent, and selec...## About you
CamiTK developer
## Product
Core in InteractiveViewer.
## Overview
In the main viewer, unselected elements are transparent, selected elements are not.
Add an option to show unselected elements as non-transparent, and selected elements with an highlighted sihouette.
This is identical to [the VTK Silhouette example](https://kitware.github.io/vtk-examples/site/Cxx/Picking/HighlightWithSilhouette/)
---
**please do not remove anything below this line**Manik BhattacharjeeManik Bhattacharjeehttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/130Add anti-aliasing support to 3D display viewer2023-07-26T16:26:46+02:00Manik BhattacharjeeAdd anti-aliasing support to 3D display viewer## About you
New CamiTK developer
## Product
Mesh display in the 3D viewer shows aliased lines.
Adding anti-aliasing support as an option would improve rendering.
## Overview
When displaying lines or meshes, there is a jagged-edge e...## About you
New CamiTK developer
## Product
Mesh display in the 3D viewer shows aliased lines.
Adding anti-aliasing support as an option would improve rendering.
## Overview
When displaying lines or meshes, there is a jagged-edge effect (a straight line in diagonal shows sharp steps in pixels) due to the way lines are rendered. Anti-aliasing techniques can improve the look of images and are available in VTK. They should be added as options in the preferences of the 3D viewer.
## Relevant logs and/or screenshots
There is a discussion in VTK forum about different ways to activate anti-aliasing in vtk, with sample images.
https://discourse.vtk.org/t/how-to-anti-alias-in-vtkrenderwindow/4556/12
---
**please do not remove anything below this line**Manik BhattacharjeeManik Bhattacharjeehttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/120The next CamiTK version should be called CamiTK 5.02021-01-28T16:07:01+01:00Emmanuel PromayonThe next CamiTK version should be called CamiTK 5.0Current CamiTK develop version (aka version 4.2.develop) should become CamiTK version 5.0
- **main reason 1:** the new viewer extension breaks the API (viewers are not singleton, they have to be accessed by name not pointer, cf #110)
- *...Current CamiTK develop version (aka version 4.2.develop) should become CamiTK version 5.0
- **main reason 1:** the new viewer extension breaks the API (viewers are not singleton, they have to be accessed by name not pointer, cf #110)
- **main reason 2:** viewer extension deserves a major version update to stand out
- The next CamiTK should be very stable as we don't plan to add any big features for a good while, it can be nicknamed as something like "LTS", which deserves a round version number
- A round version number will simplify discussion and communication (latest = stable = lts = 5.0) which stands out much more that 4.2 (very close to 4.1)
- the website explanation can be simplified if the next version is 5.0
- The next color codename is green! :smile:
Acceptance tests
- [x] all 5.0 stuff should be renamed 6.0 (deprecation should be move up one version to let people get used to it)
- [x] all 4.2 stuff should be 5.0 (not 4.2 string)
- [x] experimental website should be simplified to point to 5.0 as the new stable / LTS versionhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/118Replace Copyright text by a more discrete watermark.2021-01-19T06:51:09+01:00Emmanuel PromayonReplace Copyright text by a more discrete watermark.## About you
CamiTK developer/maintainer
## Product
CamiTK interactive viewers
## Overview
Since the update to support VTK 7, the copyright text disappeared from the right corner of the Interactive Viewer instances.
Although the copy...## About you
CamiTK developer/maintainer
## Product
CamiTK interactive viewers
## Overview
Since the update to support VTK 7, the copyright text disappeared from the right corner of the Interactive Viewer instances.
Although the copyright text was a bit 1980's it was nice to have something that was a bit like a watermark.
It was quite intrusive though (but it was possible to remove it by Right-Clicking on an interactive viewer).
The best would be to replace it by a more discrete watermark.
I suggest using a smallish CamiTK logo with some transparency in the very bottom very right corner of the viewer.
The advantage will be to encourage people to leave the logo (it is too small to be annoying in most of the case), and therefore be able to promote nice projects that use CamiTK.
→ May be have a little dialog to promote citing the article as well/instead of the logo, when the user decide to disable the logo?
---CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/116More coherent MISR tutorial actions GUI2021-01-05T07:31:05+01:00Emmanuel PromayonMore coherent MISR tutorial actions GUI## About you
CamiTK developer
## Product
Mainly camitk-imp
## Overview
During the http://misr.free.fr tutorial, there are three different things that could be improved in order to make discovering medical image analysis easier and fac...## About you
CamiTK developer
## Product
Mainly camitk-imp
## Overview
During the http://misr.free.fr tutorial, there are three different things that could be improved in order to make discovering medical image analysis easier and facilitate knowledge acquisitions:
- (easy) the action menu are not coherent (the "Display" family has "Volume Rendering" but not "Lookup Table" action, Save, Close, Save As are in a menu called "Application", which is not the same as the menu name in the menu bar
- (time consuming) the Volume Rendering action is not really easy to use (complex to setup) and appears in a separate window (and is not managed like any other actions)
- (hard) the Lookup Table action has a lot of bugs and does not allow a proper visualization/interaction with the values in the images
## What can be done
- [x] Rename the "Application" menu to "File"
- [X] Rewrite "Volume Rendering" so that it can be used like any other actions
- [X] Debug Lookup Table and improve the GUI so that it has a true pedagogical usage
- [x] Rename "Display" to "View" and move "Lookup Table", "Arbitrary Slice" to this family.
- [x] Move "Visibility" to "View"
- [X] Computed output in Otsu and Connected component should be updated automatically, visible once the action is performed, and reset at each select and should also appear in the log
- [X] Visibility toggle should be visible for the View actions
- [X] Manual filter should take the voxel range value, not the type min/max (and therefore be updated at each select
- [X] Try to fix opening file with space/special character in path on windows
- [X] better handling of mha/mhd when type is not unsigned char
- [X] Frame editor manages precision (when value <1e-6, just display 0.0)
- [x] Separate frame editor in three actions: show/hide frame, set parent frame, show/edit frame
---
**please do not remove anything below this line**CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/101viewer extension dependencies in wizard2023-06-02T16:49:24+02:00Maxime Calkaviewer extension dependencies in wizard## About you
Occasional CamiTK developer
## Product
Wizard
## Overview
Add in the dependencies of the extension the possibilities to link a viewer extension.
## Relevant logs and/or screenshots
Already implemented:
![image](/uploa...## About you
Occasional CamiTK developer
## Product
Wizard
## Overview
Add in the dependencies of the extension the possibilities to link a viewer extension.
## Relevant logs and/or screenshots
Already implemented:
![image](/uploads/d5dac9ba6884a5565013cbc41f370457/image.png)
Needed:
![image](/uploads/4c4851f8c2277b4c451ecd4129a12339/image.png)Maxime CalkaMaxime Calkahttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/93Set component extension for the viewer2020-03-04T12:42:45+01:00Maxime CalkaSet component extension for the viewer## About you
Meniscare developper
## Product
CamiTK Core
## Overview
Set the list of component extension that can be viewed inside the viewer
---
**please do not remove anything below this line**## About you
Meniscare developper
## Product
CamiTK Core
## Overview
Set the list of component extension that can be viewed inside the viewer
---
**please do not remove anything below this line**Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/92Seen viewer extension in menu and right click of the frame explorer2020-03-04T12:42:46+01:00Maxime CalkaSeen viewer extension in menu and right click of the frame explorer## About you
Meniscare developper
## Product
CamiTK Core
## Overview
Seen viewer extension in menu and right click of the frame explorer
---
**please do not remove anything below this line**## About you
Meniscare developper
## Product
CamiTK Core
## Overview
Seen viewer extension in menu and right click of the frame explorer
---
**please do not remove anything below this line**Emmanuel PromayonEmmanuel Promayon