Cool… but before I get into the explanation, let me start by saying Bubble’s learning curve is steep. So, if you haven’t done the lessons or taken advantage of any of the other great learning resources that are out there, you could find yourself struggling on your Bubble journey. Anyway, just food for thought there, and now on to the explanation.
I made the example I am about to show on my index page, and I started by creating a custom state on the page that looks like this.
I already posted a screenshot of the condition on the submit button, but what I didn’t show is that the This element isn’t clickable checkbox is checked on the button’s Appearance tab.
Next, go to your Workflow tab and create a workflow event using this option.
Then, select RadioButton A as the element, and add a step to the event that looks like this.
That step clears the custom state’s value any time RadioButton A’s value is changed. The next step in the workflow will set the now cleared custom state’s value to the list of numbers that have been selected across all of the radio buttons, and that step looks like this.
Finally, right-click on the workflow event, copy it, paste it three times, and change RadioButton A to one of the other three radio buttons so that there ends up being a workflow event for each radio button.
One key piece of the puzzle that makes this suggestion work is that Bubble doesn’t allow a list to have duplicate values in it. So, if a user has selected the same value for two or more of the radio buttons, that value will only be added to the custom state list one time, and therefore, the count of that list will never be 4 (which means the condition to make the button clickable will never be met).
Anyway, that might be a lot more than you wanted on this post, but I hope it isn’t too overwhelming, and I hope it helps you get down a good path.