Merge topic 'workflow_widget'

  STYLE: Workflow - Fix doxygen

Libs/Core/ctkWorkflow.h

@@ -87,7 +87,7 @@ public:
                              const ctkWorkflow::TransitionDirectionality directionality
                                = ctkWorkflow::Bidirectional);
 
-  /// \Determine whether a transition has already been added
+  /// \brief Determine whether a transition has already been added
   /// <ul>
   ///  <li>If a branch id is not given or is empty: a transition exists if a transition has been
   /// previously added with the same origin, destination and directionality</li>

Libs/Core/ctkWorkflowStep.h

@@ -59,11 +59,9 @@ public:
   QString description()const;
   void setDescription(const QString& newDescription);
 
-  ///
   /// Get \a statusText
   QString statusText()const;
 
-  ///
   /// Set/get whether a validationCommand has been provided in a separate QObject
   /// \note see method 2 described for validation()
   /// \sa validation()
@@ -137,7 +135,7 @@ protected:
   /// ctkWorkflowTransitionType::ValidationFailedTransition.
   ctkWorkflowIntrastepTransition* validationFailedTransition()const;
 
-  ///\brief  Reimplement this function for step-specific processing when entering a step.
+  /// \brief  Reimplement this function for step-specific processing when entering a step.
   ///
   /// To define a custom step, developers can either reimplement the onEntry() method in a subclass
   /// of ctkWorkflowStep, or create a ctkWorkflowStep instance and use signals and slots, as

Libs/Widgets/ctkWorkflowAbstractWidgetStep.h

@@ -114,35 +114,29 @@ public:
 
 protected:
 
-  ///
   /// Creates the user interface associated with this step.
   virtual void createUserInterface() = 0;
 
-  ///
   /// Prepares the step to be shown.
   virtual void showUserInterface();
 
   /// \brief Signal (emitted by the private implementation) indicating that the step's
   /// createUserInterface() method should be called.
-  ///
   /// \sa createUserInterface()
   void invokeCreateUserInterfaceCommand()const;
 
   /// \brief Signal (emitted by the private implementation) indicating that the step's
   /// createUserInterface() method has completed.
-  ///
   /// \sa createUserInterface()
   void createUserInterfaceComplete()const;
 
   /// \brief Signal (emitted by the private implementation) indicating that the step's
   /// 'showUserInterface() method should be called.
-  ///
   /// \sa showUserInterface()
   void invokeShowUserInterfaceCommand()const;
 
   /// \brief Signal (emitted by the private implementation) indicating that the step's
   /// showUserInterface() method has completed.
-  ///
   /// \sa showUserInterface()
   void showUserInterfaceComplete()const;