First of all I’m very new so my apologies if this has a very obvious solution
I’m trying to develop a Tree skill. I need to make a button unclickable until the previous one is clicked. What I think I need is to simply untick “This element isn’t clickable” when Button A is pressed. What I tried to achieve this is the following:
Created Button A and Button B
When Button A is clicked -> Create a New thing -> “Button B” (Field “Unlock” and Type yes/no, then = Yes)
Then I toggled Button B as unclickable.
Then I tried 2 things:
Went to “Button B” -> conditional -> "Search for Button B’s Unlock is yes… and I get stuck. I don’t think I need anything else, but the issues icon tells me "Page X - states must evaluate “yes or no” but this is a list of yes/nos
Went back to Button A’s workflow and added a new action “Set state of Button B Unlock = yes”
Then tried step 1, same thing happened.
This is a only a test, what I actually will need, is that Button A takes the user to a new page with an activity, when this activity is finished it must return some data into a “thing” that eventually makes the next button clickable.
@ssmusic3 I would use the chain of custom states as you suggest, but from a design principle do not use the controlA to set the custom state of a controlB. Instead, set a custom state of Control A and allow Control B to read its value using conditionals.
This allows you to scale easier if you end up wanting more things to look at status of controlA
This is an approach we use when design control systems logic, simplifies maintainability. (and depending on the safety criticality of the system, writing out is not permitted, only reading in allowed)
