Skip to content

Commit 0d9d102

Browse files
authored
Added new behavior to Output Inspector
1 parent ce16962 commit 0d9d102

File tree

4 files changed

+6
-2
lines changed

4 files changed

+6
-2
lines changed

mevislab.github.io/content/tutorials/basicmechanisms/dataimport.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,10 @@ In order to get all DICOM tags from your currently imported and selected volume,
7474

7575
![DicomTagBrowser Module](/images/tutorials/basicmechanics/DicomTagBrowser.png "DicomTagBrowser Module")
7676

77+
In MeVisLab versions later than 4.2.0 the *Output Inspector* provides the option to show the DICOM tags of the currently selected output directly. You do not need to add a separate `DicomTagBrowser` module anymore.
78+
79+
![DICOM Information in Output Inspector](/images/tutorials/basicmechanics/OutputInspectorDICOM.png "DICOM Information in Output Inspector")
80+
7781
## Segmentations / 2D Contours {#2DContours}
7882
2-dimensional contours in MeVisLab are handled via *CSO*s (**C**ontour **S**egmentation **O**bjects).
7983

mevislab.github.io/content/tutorials/basicmechanisms/macromodules/globalmacromodules.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ right-click {{< mousebutton "right" >}} the macro module to open the context men
4848
*\\MyPackageGroup\\General\\Modules\\Macros\\MyProject*.
4949

5050
{{<alert class="info" caption="Info">}}
51-
Make sure to chose *Directory Structure* as *self-contained*. This makes sure that all files of your module are stored in a single directory.
51+
If you are working with MeVisLab versions before 5.0, make sure to chose *Directory Structure* as *self-contained*. This makes sure that all files of your module are stored in a single directory. Later versions always use *self-contained*.
5252

5353
Also keep in mind that Python files are only created automatically if selected in the Project Wizard. Converting a local macro to a global macro does NOT create a Python file automatically.
5454
{{</alert>}}

mevislab.github.io/content/tutorials/basicmechanisms/macromodules/scriptingexample2.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Project Wizard, which you find under {{< menuitem "File" "Run Project Wizard" >}
2929
Now, you have to edit:
3030
1. Name: The name of your module
3131
2. Package: Select the package you like to save the macro module in.
32-
3. Directory Structure: Change to *Self-contained*
32+
3. Directory Structure: Change to *Self-contained* (this setting is only available in MeVisLab versions before 5.0.0, later versions always use *self-contained*)
3333
4. Project: Select you project name
3434

3535
Press *Next* and edit the following:
264 KB
Loading

0 commit comments

Comments
 (0)