Image has a TimeSlicedGeometry, which contains one or more SlicedGeometry3D instances (one for each time step), all of which contain one or more instances of (sub-classes of) Geometry2D (usually PlaneGeometry2D).
-Converting coordinates from the ITK physical coordinate system (which does not support rotated images) to the MITK world coordinate system should be performed via the Geometry3D of the Image, see Geometry3D::WorldToItkPhysicalPoint.
+
+Special Commands
+Introduction
+All commands in the documentation start with a backslash (\) or an at-sign (@). If you prefer you can replace all commands starting with a backslash below by their counterparts that start with an at-sign.
+
+Some commands have one or more arguments. Each argument has a certain range:
+
+ * If <sharp> braces are used the argument is a single word.
+ * If (round) braces are used the argument extends until the end of the line on which the command was found.
+ * If {curly} braces are used the argument extends until the next paragraph. Paragraphs are delimited by a blank line or by a section indicator.
+
+If [square] brackets are used the argument is optional.
+
+Here is an alphabetically sorted list of all commands with references to their documentation:
+
+ * \a
+ * \addindex
+ * \addtogroup
+ * \anchor
+ * \arg
+ * \attention
+ * \author
+ * \b
+ * \brief
+ * \bug
+ * \c
+ * \callgraph
+ * \callergraph
+ * \category
+ * \class
+ * \code
+ * \cond
+ * \copybrief
+ * \copydetails
+ * \copydoc
+ * \date
+ * \def
+ * \defgroup
+ * \deprecated
+ * \details
+ * \dir
+ * \dontinclude
+ * \dot
+ * \dotfile
+ * \e
+ * \else
+ * \elseif
+ * \em
+ * \endcode
+ * \endcond
+ * \enddot
+ * \endhtmlonly
+ * \endif
+ * \endlatexonly
+ * \endlink
+ * \endmanonly
+ * \endmsc
+ * \endverbatim
+ * \endxmlonly
+ * \enum
+ * \example
+ * \exception
+ * \extends
+ * \f$
+ * \f[
+ * \f]
+ * \f{
+ * \f}
+ * \file
+ * \fn
+ * \headerfile
+ * \hideinitializer
+ * \htmlinclude
+ * \htmlonly
+ * \if
+ * \ifnot
+ * \image
+ * \implements
+ * \include
+ * \includelineno
+ * \ingroup
+ * \internal
+ * \invariant
+ * \interface
+ * \latexonly
+ * \li
+ * \line
+ * \link
+ * \mainpage
+ * \manonly
+ * \memberof
+ * \msc
+ * \n
+ * \name
+ * \namespace
+ * \nosubgrouping
+ * \note
+ * \overload
+ * \p
+ * \package
+ * \page
+ * \par
+ * \paragraph
+ * \param
+ * \post
+ * \pre
+ * \private
+ * \privatesection
+ * \property
+ * \protected
+ * \protectedsection
+ * \protocol
+ * \public
+ * \publicsection
+ * \ref
+ * \relates
+ * \relatesalso
+ * \remarks
+ * \return
+ * \retval
+ * \sa
+ * \section
+ * \see
+ * \showinitializer
+ * \since
+ * \skip
+ * \skipline
+ * \struct
+ * \subpage
+ * \subsection
+ * \subsubsection
+ * \test
+ * \throw
+ * \todo
+ * \tparam
+ * \typedef
+ * \union
+ * \until
+ * \var
+ * \verbatim
+ * \verbinclude
+ * \version
+ * \warning
+ * \weakgroup
+ * \xmlonly
+ * \xrefitem
+ * \$
+ * \@
+ * \\
+ * \&
+ * \~
+ * \<
+ * \>
+ * \#
+ * \%
+ * \"
+
+The following subsections provide a list of all commands that are recognized by doxygen. Unrecognized commands are treated as normal text.
+--- Structural indicators ---
+\addtogroup <name> [(title)]
+
+Defines a group just like \defgroup, but in contrast to that command using the same <name> more than once will not result in a warning, but rather one group with a merged documentation and the first title found in any of the commands.
+
+The title is optional, so this command can also be used to add a number of entities to an existing group using @{ and @} like this:
+
+ /*! \addtogroup mygrp
+ * Additional documentation for group `mygrp'
+ * @{
+ */
+
+ /*!
+ * A function
+ */
+ void func1()
+ {
+ }
+
+ /*! Another function */
+ void func2()
+ {
+ }
+
+ /*! @} */
+
+See also:
+ page Grouping, sections \defgroup, \ingroup and \weakgroup.
+
+\callgraph
+
+When this command is put in a comment block of a function or method and HAVE_DOT is set to YES, then doxygen will generate a call graph for that function (provided the implementation of the function or method calls other documented functions). The call graph will generated regardless of the value of CALL_GRAPH.
+
+Note:
+ The completeness (and correctness) of the call graph depends on the doxygen code parser which is not perfect.
+
+\callergraph
+
+When this command is put in a comment block of a function or method and HAVE_DOT is set to YES, then doxygen will generate a caller graph for that function (provided the implementation of the function or method calls other documented functions). The caller graph will generated regardless of the value of CALLER_GRAPH.
+
+Note:
+ The completeness (and correctness) of the caller graph depends on the doxygen code parser which is not perfect.
+
+\category <name> [<header-file>] [<header-name>]
+
+For Objective-C only: Indicates that a comment block contains documentation for a class category with name <name>. The arguments are equal to the \class command.
+
+See also:
+ section \class.
+
+\class <name> [<header-file>] [<header-name>]
+
+Indicates that a comment block contains documentation for a class with name <name>. Optionally a header file and a header name can be specified. If the header-file is specified, a link to a verbatim copy of the header will be included in the HTML documentation. The <header-name> argument can be used to overwrite the name of the link that is used in the class documentation to something other than <header-file>. This can be useful if the include name is not located on the default include path (like <X11/X.h>). With the <header-name> argument you can also specify how the include statement should look like, by adding either quotes or sharp brackets around the name. Sharp brackets are used if just the name is given. Note that the last two arguments can also specified using the \headerfile command.
+
+Example:
+
+ /* A dummy class */
+
+ class Test
+ {
+ };
+
+ /*! \class Test class.h "inc/class.h"
+ * \brief This is a test class.
+ *
+ * Some details about the Test class
+ */
+
+ Click here for the corresponding HTML documentation that is generated by doxygen.
+
+\def <name>
+
+Indicates that a comment block contains documentation for a #define macro.
+
+Example:
+
+ /*! \file define.h
+ \brief testing defines
+
+ This is to test the documentation of defines.
+ */
+
+ /*!
+ \def MAX(x,y)
+ Computes the maximum of \a x and \a y.
+ */
+
+ /*!
+ Computes the absolute value of its argument \a x.
+ */
+ #define ABS(x) (((x)>0)?(x):-(x))
+ #define MAX(x,y) ((x)>(y)?(x):(y))
+ #define MIN(x,y) ((x)>(y)?(y):(x))
+ /*!< Computes the minimum of \a x and \a y. */
+
+ Click here for the corresponding HTML documentation that is generated by doxygen.
+
+\defgroup <name> (group title)
+
+Indicates that a comment block contains documentation for a group of classes, files or namespaces. This can be used to categorize classes, files or namespaces, and document those categories. You can also use groups as members of other groups, thus building a hierarchy of groups.
+
+The <name> argument should be a single-word identifier.
+Indicates that a comment block contains documentation for a directory. The "path fragment" argument should include the directory name and enough of the path to be unique w.r.t. the other directories in the project. The SHOW_DIRECTORIES option determines whether or not the directory information is shown and the STRIP_FROM_PATH option determines what is stripped from the full path before it appears in the output.
+\enum <name>
+
+Indicates that a comment block contains documentation for an enumeration, with name <name>. If the enum is a member of a class and the documentation block is located outside the class definition, the scope of the class should be specified as well. If a comment block is located directly in front of an enum declaration, the \enum comment may be omitted.
+
+Note:
+ The type of an anonymous enum cannot be documented, but the values of an anonymous enum can.
+
+Example:
+
+ class Test
+ {
+ public:
+ enum TEnum { Val1, Val2 };
+
+ /*! Another enum, with inline docs */
+ enum AnotherEnum
+ {
+ V1, /*!< value 1 */
+ V2 /*!< value 2 */
+ };
+ };
+
+ /*! \class Test
+ * The class description.
+ */
+
+ /*! \enum Test::TEnum
+ * A description of the enum type.
+ */
+
+ /*! \var Test::TEnum Test::Val1
+ * The description of the first enum value.
+ */
+
+ Click here for the corresponding HTML documentation that is generated by doxygen.
+
+\example <file-name>
+
+Indicates that a comment block contains documentation for a source code example. The name of the source file is <file-name>. The text of this file will be included in the documentation, just after the documentation contained in the comment block. All examples are placed in a list. The source code is scanned for documented members and classes. If any are found, the names are cross-referenced with the documentation. Source files or directories can be specified using the EXAMPLE_PATH tag of doxygen's configuration file.
+
+If <file-name> itself is not unique for the set of example files specified by the EXAMPLE_PATH tag, you can include part of the absolute path to disambiguate it.
+
+If more that one source file is needed for the example, the \include command can be used.
+
+Example:
+
+ /** A Test class.
+ * More details about this class.
+ */
+
+ class Test
+ {
+ public:
+ /** An example member function.
+ * More details about this function.
+ */
+ void example();
+ };
+
+ void Test::example() {}
+
+ /** \example example_test.cpp
+ * This is an example of how to use the Test class.
+ * More details about this example.
+ */
+
+ Where the example file example_test.cpp looks as follows:
+
+ void main()
+ {
+ Test t;
+ t.example();
+ }
+
+ Click here for the corresponding HTML documentation that is generated by doxygen.
+
+See also:
+ section \include.
+
+\extends <name>
+
+This command can be used to manually indicate an inheritance relation, when the programming language does not support this concept natively (e.g. C).
+
+The file manual.c in the example directory shows how to use this command.
+Click here for the corresponding HTML documentation that is generated by doxygen.
+
+See also:
+ section \implements and section \memberof
+
+\file [<name>]
+
+Indicates that a comment block contains documentation for a source or header file with name <name>. The file name may include (part of) the path if the file-name alone is not unique. If the file name is omitted (i.e. the line after \file is left blank) then the documentation block that contains the \file command will belong to the file it is located in.
+
+Important:
+ The documentation of global functions, variables, typedefs, and enums will only be included in the output if the file they are in is documented as well.
+
+Example:
+
+ /** \file file.h
+ * A brief file description.
+ * A more elaborated file description.
+ */
+
+ /**
+ * A global integer value.
+ * More details about this value.
+ */
+ extern int globalValue;
+
+ Click here for the corresponding HTML documentation that is generated by doxygen.
+
+Note:
+ In the above example JAVADOC_AUTOBRIEF has been set to YES in the configuration file.
+
+\fn (function declaration)
+
+Indicates that a comment block contains documentation for a function (either global or as a member of a class). This command is only needed if a comment block is not placed in front (or behind) the function declaration or definition.
+
+If your comment block is in front of the function declaration or definition this command can (and to avoid redundancy should) be omitted.
+
+A full function declaration including arguments should be specified after the \fn command on a single line, since the argument ends at the end of the line!
+
+Warning:
+ Do not use this command if it is not absolutely needed, since it will lead to duplication of information and thus to errors.
+ * \exception std::out_of_range parameter is out of range.
+ * \return a character pointer.
+ */
+
+ Click here for the corresponding HTML documentation that is generated by doxygen.
+
+See also:
+ section \var and \typedef.
+
+\headerfile <header-file> [<header-name>]
+
+Intended to be used for class, struct, or union documentation, where the documentation is in front of the definition. The arguments of this command are the same as the second and third argument of \cmdclass. The header-file name refers to the file that should by included by the application to obtain the definition of the class, struct, or union. The <header-name> argument can be used to overwrite the name of the link that is used in the class documentation to something other than <header-file>. This can be useful if the include name is not located on the default include path (like <X11/X.h>).
+
+With the <header-name> argument you can also specify how the include statement should look like, by adding either double quotes or sharp brackets around the name. By default sharp brackets are used if just the name is given.
+
+If a pair of double quotes is given for either the header-file or header-name argument, the current file (in which the command was found) will be used but with quotes. So for a comment block with a \headerfile command inside a file test.h, the following three commands are equivalent:
+
+ \headerfile test.h "test.h"
+ \headerfile test.h ""
+ \headerfile ""
+
+To get sharp brackets you do not need to specify anything, but if you want to be explicit you could use any of the following:
+
+ \headerfile test.h <test.h>
+ \headerfile test.h <>
+ \headerfile <>
+
+To globally reverse the default include representation to local includes you can set FORCE_LOCAL_INCLUDES to YES.
+
+To disable the include information altogether set SHOW_INCLUDE_FILES to NO.
+\hideinitializer
+
+By default the value of a define and the initializer of a variable are displayed unless they are longer than 30 lines. By putting this command in a comment block of a define or variable, the initializer is always hidden.
+
+See also:
+ section \showinitializer.
+
+\implements <name>
+
+This command can be used to manually indicate an inheritance relation, when the programming language does not support this concept natively (e.g. C).
+
+The file manual.c in the example directory shows how to use this command.
+Click here for the corresponding HTML documentation that is generated by doxygen.
+
+See also:
+ section \extends and section \memberof
+
+\ingroup (<groupname> [<groupname> <groupname>])
+
+If the \ingroup command is placed in a comment block of a class, file or namespace, then it will be added to the group or groups identified by <groupname>.
+
+See also:
+ page Grouping, sections \defgroup, \addtogroup and \weakgroup
+Indicates that a comment block contains documentation for an interface with name <name>. The arguments are equal to the \class command.
+
+See also:
+ section \class.
+
+\internal
+
+This command writes the message `For internal use only' to the output and all text after an \internal command until the end of the comment block or the end of the section (whichever comes first) is marked as "internal".
+
+If the \internal command is put inside a section (see for example \section) all subsection after the command are considered to be internal as well. Only a new section at the same level will be visible again.
+
+You can use INTERNAL_DOCS in the config file to show or hide the internal documentation.
+\mainpage [(title)]
+
+If the \mainpage command is placed in a comment block the block is used to customize the index page (in HTML) or the first chapter (in $\mbox{\LaTeX}$).
+
+The title argument is optional and replaces the default title that doxygen normally generates. If you do not want any title you can specify notitle as the argument of \mainpage.
+
+Here is an example:
+
+/*! \mainpage My Personal Index Page
+ *
+ * \section intro_sec Introduction
+ *
+ * This is the introduction.
+ *
+ * \section install_sec Installation
+ *
+ * \subsection step1 Step 1: Opening the box
+ *
+ * etc...
+ */
+
+You can refer to the main page using \ref index (if the treeview is disabled, otherwise you should use \ref main).
+
+See also:
+ section \section, section \subsection and section \page.
+
+\memberof <name>
+
+This command make a function a member of a class in a similar way as \relates does, only with this command the function is represented as a real member of the class. This can be useful when the programming language does not support the concept of member functions natively (e.g. C).
+
+It is also possible to use this command together with \public, \protected or \private.
+
+The file manual.c in the example directory shows how to use this command.
+Click here for the corresponding HTML documentation that is generated by doxygen.
+
+See also:
+ sections \extends, \implements, \public, \protected and \private.
+
+\name (header)
+
+This command turns a comment block into a header definition of a member group. The comment block should be followed by a //@{ ... //@} block containing the members of the group.
+
+See section Member Groups for an example.
+\namespace <name>
+
+Indicates that a comment block contains documentation for a namespace with name <name>.
+\nosubgrouping
+
+This command can be put in the documentation of a class. It can be used in combination with member grouping to avoid that doxygen puts a member group as a subgroup of a Public/Protected/Private/... section.
+\overload [(function declaration)]
+
+This command can be used to generate the following standard text for an overloaded member function:
+
+`This is an overloaded member function, provided for convenience. It differs from the above function only in what argument(s) it accepts.'
+
+If the documentation for the overloaded member function is not located in front of the function declaration or definition, the optional argument should be used to specify the correct function.
+
+Any other documentation that is inside the documentation block will by appended after the generated message.
+
+Note 1:
+ You are responsible that there is indeed an earlier documented member that is overloaded by this one. To prevent that document reorders the documentation you should set SORT_MEMBER_DOCS to NO in this case.
+
+Note 2:
+ The \overload command does not work inside a one-line comment.
+ * This command draws a rectangle with a left upper corner at ( \a x , \a y ),
+ * width \a w and height \a h.
+ */
+
+ /*!
+ * \overload void Test::drawRect(const Rect &r)
+ */
+
+
+ Click here for the corresponding HTML documentation that is generated by doxygen.
+
+\package <name>
+
+Indicates that a comment block contains documentation for a Java package with name <name>.
+\page <name> (title)
+
+Indicates that a comment block contains a piece of documentation that is not directly related to one specific class, file or member. The HTML generator creates a page containing the documentation. The $\mbox{\LaTeX}$ generator starts a new section in the chapter `Page documentation'.
+
+Example:
+
+ /*! \page page1 A documentation page
+ Leading text.
+ \section sec An example section
+ This page contains the subsections \ref subsection1 and \ref subsection2.
+ For more info see page \ref page2.
+ \subsection subsection1 The first subsection
+ Text.
+ \subsection subsection2 The second subsection
+ More text.
+ */
+
+ /*! \page page2 Another page
+ Even more info.
+ */
+
+ Click here for the corresponding HTML documentation that is generated by doxygen.
+
+Note:
+ The <name> argument consists of a combination of letters and number digits. If you wish to use upper case letters (e.g. MYPAGE1), or mixed case letters (e.g. MyPage1) in the <name> argument, you should set CASE_SENSE_NAMES to YES. However, this is advisable only if your file system is case sensitive. Otherwise (and for better portability) you should use all lower case letters (e.g. mypage1) for <name> in all references to the page.
+
+See also:
+ section \section, section \subsection, and section \ref.
+
+\private
+
+Indicates that the member documented in the comment block is private, i.e., should only be accessed by other members in the same class.
+
+Note that Doxygen automatically detects the protection level of members in object-oriented languages. This command is intended for use only when the language does not support the concept of protection level natively (e.g. C, PHP 4).
+
+For starting a section of private members, in a way similar to the "private:" class marker in C++, use \privatesection.
+
+See also:
+ sections \memberof, \public, and \protected.
+
+\property (qualified property name)
+
+Indicates that a comment block contains documentation for a property (either global or as a member of a class). This command is equivalent to \var and \fn.
+
+See also:
+ section \fn and \var.
+
+\protected
+
+Indicates that the member documented in the comment block is protected, i.e., should only be accessed by other members in the same or derived classes.
+
+Note that Doxygen automatically detects the protection level of members in object-oriented languages. This command is intended for use only when the language does not support the concept of protection level natively (e.g. C, PHP 4).
+
+For starting a section of protected members, in a way similar to the "protected:" class marker in C++, use \protectedsection.
+
+See also:
+ sections \memberof, \public, and \private.
+
+\protocol <name> [<header-file>] [<header-name>]
+
+Indicates that a comment block contains documentation for a protocol in Objective-C with name <name>. The arguments are equal to the \class command.
+
+See also:
+ section \class.
+
+\public
+
+Indicates that the member documented in the comment block is public, i.e., can be accessed by any other class or function.
+
+Note that Doxygen automatically detects the protection level of members in object-oriented languages. This command is intended for use only when the language does not support the concept of protection level natively (e.g. C, PHP 4).
+
+For starting a section of public members, in a way similar to the "public:" class marker in C++, use \publicsection.
+
+See also:
+ sections \memberof, \protected and \private.
+
+\relates <name>
+
+This command can be used in the documentation of a non-member function <name>. It puts the function inside the `related function' section of the class documentation. This command is useful for documenting non-friend functions that are nevertheless strongly coupled to a certain class. It prevents the need of having to document a file, but only works for functions.
+
+Example:
+
+ /*!
+ * A String class.
+ */
+
+ class String
+ {
+ friend int strcmp(const String &,const String &);
+ };
+
+ /*!
+ * Compares two strings.
+ */
+
+ int strcmp(const String &s1,const String &s2)
+ {
+ }
+
+ /*! \relates String
+ * A string debug function.
+ */
+ void stringDebug()
+ {
+ }
+
+ Click here for the corresponding HTML documentation that is generated by doxygen.
+
+\relatesalso <name>
+
+This command can be used in the documentation of a non-member function <name>. It puts the function both inside the `related function' section of the class documentation as well as leaving its normal file documentation location. This command is useful for documenting non-friend functions that are nevertheless strongly coupled to a certain class. It only works for functions.
+\showinitializer
+
+By default the value of a define and the initializer of a variable are only displayed if they are less than 30 lines long. By putting this command in a comment block of a define or variable, the initializer is shown unconditionally.
+
+See also:
+ section \hideinitializer.
+
+\struct <name> [<header-file>] [<header-name>]
+
+Indicates that a comment block contains documentation for a struct with name <name>. The arguments are equal to the \class command.
+
+See also:
+ section \class.
+
+\typedef (typedef declaration)
+
+Indicates that a comment block contains documentation for a typedef (either global or as a member of a class). This command is equivalent to \var and \fn.
+
+See also:
+ section \fn and \var.
+
+\union <name> [<header-file>] [<header-name>]
+
+Indicates that a comment block contains documentation for a union with name <name>. The arguments are equal to the \class command.
+
+See also:
+ section \class.
+
+\var (variable declaration)
+
+Indicates that a comment block contains documentation for a variable or enum value (either global or as a member of a class). This command is equivalent to \typedef and \fn.
+
+See also:
+ section \fn and \typedef.
+
+\weakgroup <name> [(title)]
+
+Can be used exactly like \addtogroup, but has a lower priority when it comes to resolving conflicting grouping definitions.
+
+See also:
+ page Grouping and \addtogroup.
+
+--- Section indicators ---
+\attention { attention text }
+
+Starts a paragraph where a message that needs attention may be entered. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent \attention commands will be joined into a single paragraph. The \attention command ends when a blank line or some other sectioning command is encountered.
+\author { list of authors }
+
+Starts a paragraph where one or more author names may be entered. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent \author commands will be joined into a single paragraph. Each author description will start a new line. Alternatively, one \author command may mention several authors. The \author command ends when a blank line or some other sectioning command is encountered.
+
+Example:
+
+ /*! \class WindowsNT
+ * \brief Windows Nice Try.
+ * \author Bill Gates
+ * \author Several species of small furry animals gathered together
+ * in a cave and grooving with a pict.
+ * \version 4.0
+ * \date 1996-1998
+ * \bug It crashes a lot and requires huge amounts of memory.
+ * \bug The class introduces the more bugs, the longer it is used.
+ * \warning This class may explode in your face.
+ * \warning If you inherit anything from this class, you're doomed.
+ */
+
+ class WindowsNT {};
+
+ Click here for the corresponding HTML documentation that is generated by doxygen.
+
+\brief {brief description}
+
+Starts a paragraph that serves as a brief description. For classes and files the brief description will be used in lists and at the start of the documentation page. For class and file members, the brief description will be placed at the declaration of the member and prepended to the detailed description. A brief description may span several lines (although it is advised to keep it brief!). A brief description ends when a blank line or another sectioning command is encountered. If multiple \brief commands are present they will be joined. See section \author for an example.
+
+Synonymous to \short.
+\bug { bug description }
+
+Starts a paragraph where one or more bugs may be reported. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent \bug commands will be joined into a single paragraph. Each bug description will start on a new line. Alternatively, one \bug command may mention several bugs. The \bug command ends when a blank line or some other sectioning command is encountered. See section \author for an example.
+\cond [<section-label>]
+
+Starts a conditional section that ends with a corresponding \endcond command, which is typically found in another comment block. The main purpose of this pair of commands is to (conditionally) exclude part of a file from processing (in older version of doxygen this could only be achieved using C preprocessor commands).
+
+The section between \cond and \endcond commands can be included by adding its section label to the ENABLED_SECTIONS configuration option. If the section label is omitted, the section will be excluded from processing unconditionally.
+
+For conditional sections within a comment block one should use a \if ... \endif block.
+
+Conditional sections can be nested. In this case a nested section will only be shown if it and its containing section are included.
+
+Here is an example showing the commands in action:
+
+/** An interface */
+class Intf
+{
+ public:
+ /** A method */
+ virtual void func() = 0;
+
+ /// @cond TEST
+
+ /** A method used for testing */
+ virtual void test() = 0;
+
+ /// @endcond
+};
+
+/// @cond DEV
+/*
+ * The implementation of the interface
+ */
+class Implementation : public Intf
+{
+ public:
+ void func();
+
+ /// @cond TEST
+ void test();
+ /// @endcond
+
+ /// @cond
+ /** This method is obsolete and does
+ * not show up in the documentation.
+ */
+ void obsolete();
+ /// @endcond
+};
+
+/// @endcond
+
+The output will be different depending on whether or not ENABLED_SECTIONS contains TEST, or DEV
+\date { date description }
+
+Starts a paragraph where one or more dates may be entered. The paragraph will be indented. The text of the paragraph has no special internal structure. All visual enhancement commands may be used inside the paragraph. Multiple adjacent \date commands will be joined into a single paragraph. Each date description will start on a new line. Alternatively, one \date command may mention several dates. The \date command ends when a blank line or some other sectioning command is encountered. See section \author for an example.
+\deprecated{For ITK v3.8 and older: Converting coordinates from the ITK physical coordinate system (which did not support rotated images in v3.8 and older) to the MITK world coordinate system should be performed via the Geometry3D of the Image, see Geometry3D::WorldToItkPhysicalPoint.}
+
As a reminder: Geometry instances referring to images need a slightly different definition of corners, see Geometry3D::SetImageGeometry. This is usualy automatically called by Image.