That is how it works, unless you change it. Any object with a Selected state works that way, which is the built-in nature of the Selected state. That functioning can be defeated by selecting several objects and making them a button set, which changes their function. Only one of a button set can be selected at a time.
Unless you create a trigger to change the state to selected. Such a manually created trigger will create conflict with the built-in trigger in unpleasant ways and times that can't be predicted.
No, the one that finally worked was Visited. So now the user can select option A, C, and E, for example, and then click Submit.
However, the user can't select option A and then change his mind and un-select it by clicking it again. I guess the easiest route at this point is a "Clear" button.
5 Replies
That is how it works, unless you change it. Any object with a Selected state works that way, which is the built-in nature of the Selected state. That functioning can be defeated by selecting several objects and making them a button set, which changes their function. Only one of a button set can be selected at a time.
Unless you create a trigger to change the state to selected.
Such a manually created trigger will create conflict with the built-in trigger in unpleasant ways and times that can't be predicted.
But the "glow" that appears around a selected option disappears when the next option is selected.
Because this is a "pick many", I want the user to see a glow around each and every option selected before they hit submit.
Is the glow part of the Down state?
You can edit the selected state to put a glow on it. If it is checked, it is selected.
No, the one that finally worked was Visited. So now the user can select option A, C, and E, for example, and then click Submit.
However, the user can't select option A and then change his mind and un-select it by clicking it again. I guess the easiest route at this point is a "Clear" button.
Do you have button set applied? Using visited is not a great fix