#MSG_function_register (and maybe #MSG_function_register_default)
-# Launch your processes from a deployment file with #MSG_launch_application
-# Run the simulation with #MSG_main
-
-@htmlonly <!-- DOXYGEN_NAVBAR_LABEL="Simulation Control" --> @endhtmlonly
*/
/** @defgroup m_process_management Process Management Functions
* @brief This section describes the task structure of MSG
* (#msg_task_t) and the functions for managing it. See
* \ref msg_task_usage to see how to put the tasks in action.
- *
- * \htmlonly <!-- DOXYGEN_NAVBAR_LABEL="Tasks" --> \endhtmlonly
*/
/** @defgroup msg_mailbox_management Mailbox Management Functions
* @ingroup MSG_API
* @brief This section describes the mailbox structure of MSG
* (#msg_mailbox_t) and the functions for managing it.
- *
- * \htmlonly <!-- DOXYGEN_NAVBAR_LABEL="Mailbox" --> \endhtmlonly
*/
/** @defgroup msg_task_usage Task Actions
@ingroup MSG_API
@brief This section describes the functions allowing to build trace-driven simulations.
-\htmlonly <!-- DOXYGEN_NAVBAR_LABEL="Trace-Driven" --> \endhtmlonly
-
This is very handy when you want to test an algorithm or protocol that
does nothing unless it receives some events from outside. For example,
a P2P protocol reacts to requests from the user, but does nothing if
@ingroup MSG_API
@brief .
-Finding the right example in examples/msg is sometimes difficult. This list aims at helping you to find the example from which you can learn what you want to.
-
-\section msg_bsc_ex Basic examples
+Finding the right example in examples/msg is sometimes difficult. This list aims at helping you to find the example from which you can learn what you want to.
+ - @ref msg_ex_basic
+ - @ref msg_ex_async
+ - @ref msg_ex_process
+ - @ref msg_ex_tracing
+ - @ref msg_ex_tracing_user_variables
+ - @ref msg_ex_models
+ - @ref msg_ex_io
+ - @ref msg_ex_actions
+ - @ref msg_ex_full_apps
+ - @ref msg_ex_misc
+
+\section msg_ex_basic Basic examples
*/
