diff --git a/mevislab.github.io/content/tutorials/basicmechanisms/dataimport.md b/mevislab.github.io/content/tutorials/basicmechanisms/dataimport.md index 230369399..23d33e5be 100644 --- a/mevislab.github.io/content/tutorials/basicmechanisms/dataimport.md +++ b/mevislab.github.io/content/tutorials/basicmechanisms/dataimport.md @@ -74,6 +74,10 @@ In order to get all DICOM tags from your currently imported and selected volume, ![DicomTagBrowser Module](/images/tutorials/basicmechanics/DicomTagBrowser.png "DicomTagBrowser Module") +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. + +![DICOM Information in Output Inspector](/images/tutorials/basicmechanics/OutputInspectorDICOM.png "DICOM Information in Output Inspector") + ## Segmentations / 2D Contours {#2DContours} 2-dimensional contours in MeVisLab are handled via *CSO*s (**C**ontour **S**egmentation **O**bjects). diff --git a/mevislab.github.io/content/tutorials/basicmechanisms/macromodules/globalmacromodules.md b/mevislab.github.io/content/tutorials/basicmechanisms/macromodules/globalmacromodules.md index 27f3a2793..48bb74379 100644 --- a/mevislab.github.io/content/tutorials/basicmechanisms/macromodules/globalmacromodules.md +++ b/mevislab.github.io/content/tutorials/basicmechanisms/macromodules/globalmacromodules.md @@ -48,7 +48,7 @@ right-click {{< mousebutton "right" >}} the macro module to open the context men *\\MyPackageGroup\\General\\Modules\\Macros\\MyProject*. {{}} -Make sure to chose *Directory Structure* as *self-contained*. This makes sure that all files of your module are stored in a single directory. +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*. 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. {{}} diff --git a/mevislab.github.io/content/tutorials/basicmechanisms/macromodules/scriptingexample2.md b/mevislab.github.io/content/tutorials/basicmechanisms/macromodules/scriptingexample2.md index 3b4af6ee2..5e3a70846 100644 --- a/mevislab.github.io/content/tutorials/basicmechanisms/macromodules/scriptingexample2.md +++ b/mevislab.github.io/content/tutorials/basicmechanisms/macromodules/scriptingexample2.md @@ -29,7 +29,7 @@ Project Wizard, which you find under {{< menuitem "File" "Run Project Wizard" >} Now, you have to edit: 1. Name: The name of your module 2. Package: Select the package you like to save the macro module in. -3. Directory Structure: Change to *Self-contained* +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*) 4. Project: Select you project name Press *Next* and edit the following: diff --git a/mevislab.github.io/static/images/tutorials/basicmechanics/OutputInspectorDICOM.png b/mevislab.github.io/static/images/tutorials/basicmechanics/OutputInspectorDICOM.png new file mode 100644 index 000000000..ad932ec4d Binary files /dev/null and b/mevislab.github.io/static/images/tutorials/basicmechanics/OutputInspectorDICOM.png differ