Multiple events can be executed based on its priority or pre-defined sequence.
For instance, for complex-menu design, I designed a component which contains 4 buttons and each button can trigger a corresponding panel. It is painful to design the button click and panel switching logic using SLS.
Currently, I am designing the events of this kind of complex menu using following steps:
- If Button A is clicked, make Button A unclickable,
- Remove “Hidden” Flag of Panel A
- Add “Hidden” Flag of Panel B, Panel C and Panel D.
- Make Button B, Button C, Button D clickable
- Repeat Step 1~Step 4 for all other Buttons.
However, if I can define the event sequence, I can turn Button A, Button B, Button C and Button D (including corresponding panels) into components (Button Component and Panel Component), then the steps can be simplified.
Button Ais clicked, add “
Clickable” Flag to Button Component, and remove “
Clickable” Flag of Button A.
- Add “
Hidden” Flag of Panel Component, and remove “
Hidden” Flag of Panel A.
- Repeat Step 1~Step 2 for all other buttons.
Currently, since the “Component” does not support “Sequential Event Execution” function, even if you add “Hidden” flag of a component, and remove “Hidden” flag of its member, the component member will still be hidden.
It is described above in a painful way.
So many imaginable convenience in Complex UI design.