The current module selector history works like an undo/redo action history: if we go back in the history and perform a different action that it was originally in the history it removes all the "next" actions. This is a necessary behavior for undo/redo stacks (as it is not possible to apply a "next" action on a changed current state), but it is an unnecessary inconvenience for a module history.

In case of a model history we can simply insert a new module into the history, as there is no actual processing action is performed, so there is no inconsistency in application state (we can switch to another module regardless of what previous modules we visited in what order).

Example:

Current behavior:

• Open Slicer
• Go to Volumes
• Go to Model Maker
• Go to Transforms
• Go back to the Welcome page
• Download a sample data
• Click "next" => ERROR!!! next list is empty, the previously selected modules are all lost (the "previous" module list only contains the Welcome module)

Correct behavior:

• Open Slicer
• Go to Volumes
• Go to Model Maker
• Go to Transforms
• Go back to the Welcome page
• Download a sample data
• Click "next" => Volumes module is opened