Forum Discussion
Limit to number of button actions?
The text boxes with the definitions have solid fills (or, at least, some of them do; I didn't check every one).
Because there are no triggers to hide a definition after it is set to Normal, a definition won't appear if it is below another definition with a solid fill.
The relatively easy fix for this:
- Use just 1 text box, with the Normal state showing the directions.
- Make a custom state for each regulation.
- Each button then needs just one trigger: to show the corresponding state.
By the way, I noticed that the buttons have different colors for their visited states. If that's intentional, there should be an explanation of what each color stands for. If not, then use the Formal Painter to give all the buttons the same Visited state.
BRILLIANT! Thanks Judy. I never thought to make the definitions states. The colors are supposed to indicate if it's a consumer reg (yellow) or asset security state (green), or neither (blue) but I guess I haven't made that terribly clear. I'll fix that. The goal is to help them see that regs do different things, and this is their first exposure to them so I'm doing things with familiarity at this point.
Thanks for your help!