Loop (circulation) in Axure is a feature we will often use. Most of the articles on loop are still about how to make the loop effect. There is little research on the dimensions of the loop and the action that can be implemented. Today, let's think deeply about the loop in Axure.
I divided the dimension of the loop into the following aspects. First, according to whether it is automatically triggered, it is divided into Passive and Active. When a component is loaded automatically, it is passive, and it requires active operation by the user, which is active.
Passive VS active
If the loop is triggered passively by the widget, it is passive. For example, it is triggered automatically when loaded; If the loop is triggered by the user action, for example, when the user clicks a button, it is active.
Carousel loops automatically when loaded
Generally speaking, a loop completed by an event is realized by judging different conditions in cases.
As shown in the image above, the loop is realized by judging the selection states.
If the loop is completed through the widget's own events, it is Self; If it is completed through the events of another widget, it is Intermediary.
As shown in the above image, the loop of the blue button is triggered by another button, so the loop is implemented through the intermediate.
There are many actions that a loop can perform on a target. Theoretically, most actions in Axure can implement loops, such as move, set size, show/hide, and select/unselect widgets.
Most actions in Axure can implement loop
By determining action a loop realized, different looping effects can be achieved.
If you have any questions and suggestions, please leave a message.
Well Joe @AxureBoutique, a technology writer and teacher, focuses on Axure prototype design and product design.