Excellent, scrolling through a dozen videos: those with logic made it even more complex than the ones without. Your take is brilliant, well done! Following your channel now, you've got awesome design tips, and you're very clear. Kudos to you sir!
I would suggest setting the name of the variables to semantically match the options. So "Starting Active/Inactive" in this case would become "Notifications Yes/No". At 5:45 the action would read: "Set variable 'Notifications Yes' to inactive", which is much easier to maintain
Around 2:22, I believe the issue isn't that the component instance is inside a frame, but it's the fact that it's inside another instance (of another component) named Form
Thanks a lot for the tutorial. I tried to do a radio button exercise with 4 multiple choices and it was kind of hard. Although variables are created to reduce the number of variants, due to Figma's limited capabilities, I find that it's just easier to create all possible variants, assign a string variable that matches with one of the variants, use "set variable" to go from variant A to variant B upon clicking.
I would like to do this based on the game inventory checkbox. There are five images, each has a state before clicking and after clicking . How do I create so that the selected image takes the post-click state, and the previously selected image turns into the pre-click state?
@@ossimatasaho5977 @UICollectiveDesign, if you looking for chnage in the value of the dropdown then it is easily possible by using string variable. Define string variable first and then assign it to the first value from the list of dropdown and then prototype using set variable and then change to select value. Hope this will help.
Cant we just make these two options one component (with two states - x highlighted, y highlighted) instead of linking 2 separate components through variables?
Do you really need modes to achieve that? Seems like you're just manipulating values of variables; there is always the same mode selected. Or did I miss something?
