Liliybiri has raised an excellent point.
Since it might be possible for the user to click multiple times on the same button and increment the tracking variable without selecting different items, your Conditional Action would need to first perform a check to see if the boolean variable for the specific object has a value of 0, and only if that is TRUE then increment the tracking variable and assign the Boolean to 1.
So you definitely DO need a variable for each object as well as a tracking variable.
Yes, Rod that is another way of solving it. In the previous thread I suggested summarizing the individual Booleans, but the user had only 4 interactive objects. Second reason was that it seemed easier to explain and understand because the user was pretty new to advanced actions. May I list up the three possibilities?
- If the user is allowed to click only once on a button, and you don't need to remember which buttons have been clicked, only a counter is necessary. When incrementing that counter, you disable the button that has just been clicked, thus avoiding that it can be clciked again. The second decision will check the value of the counter. This is the most simple solution.
- If the user is allowed to click each button multiple times, you need both the counter and the individual Booleans. To avoid incrementing the counter by a click on a button that has already been clicked, you calculate the counter by summarizing all the Booleans. Cumbersome with advanced actions if you have a lot of buttons because each Expression command can only use two terms. That is why I suggested using a JS math function.
- Your last proposal: add a decision (probably- that is conditional and increments the counter only when the Boolean for that button is still set to 0.