Sequence allow you to navigate between views using the "Move" navigation methods. These are, however, not always the most efficient way of navigating. This is because in order for your Move to happen on form post (via Button or any other control), the control causing the Move to occur must exist, this means that the page on which it sits must exist. Therefore, before your Move to load the new control, your previous control must load as well. This is just how ASP.NET works (remember, in web development, every time you access a page the page has to be completely recreated; controls included).

In order to increase efficiency, Themelia Pro allows you to communicate with some entities using Messages (part of something called "Themelia state"). There are many ways to use Messages, but one of the most streamlined ways is via the MessageButton control. This control allows you to set a message to send to the server when it is clicked. Below is an example of a message button control:

<t:MessageButton Message="Sequence@Next" runat="server" Text="Go to next view" />

There's a special message pattern you can follow in order to communicate with sequences.

These patterns are as follows:

Sequence@Next

Moves to the next view

Sequence@Previous

Moves to the previous view

Sequence@First

Moves to the next view

Sequence@Last

Moves to the next view

Sequence@Jump#VIEWNAME

Moves to the view specified by VIEWNAME.

By using these, you allow Themelia to know which control to load without having to load up the original control, thus increasing efficiency.

Here's an example of jumping to the "Create" view:

<t:MessageButton Message="Sequence@Jump#Create" runat="server" Text="Go to create" />