Forum Discussion
Problem with States on Custom Buttons
Button glitches happen. Sometimes, as Nedim pointed out, creating new ones fixes the glitch.
I don't think variables are needed for tracking in this situation, though. When an object has a Selected state and a Visited state, a trigger will recognize it as Visited even though it will show as Selected when first clicked. (Yup. They made the program smart enough to know that an object that's been selected has also been visited. 🤣)
- If the object isn't in a button set, it will toggle between Visited and Selected on subsequent clicks.
- If the object is in a button set, it will change to Visited when another object in the button set is Selected.
Here's more info about built-in states: PRIMER: Take advantage of built-in states | E-Learning Heroes
I think you should consider adding variables to track the visited layers instead. The last clicked button will never change to the Visited state unless another button is clicked.
As for the button states, it appears to be a glitch that most likely occurred while recreating the buttons. I duplicated the Tab 1 button and used it for the other three tabs.
Please check and test the attached file for more details.
Those triggers don't look complicated at all. I will remember them and might use them in the future for a project. Thanks for the demo file.