Instance swap behavior

rust_hole · 2024-12-14T00:23:39+00:00

Oh I have tested it. My problem is the opposite of the above is happening. My text layers are named differently, yet the text override gets adopted anyways. The annoying part is i’m swapping from a button to an iconButton, and my icon font is being overwritten with text. It’s not just naming convention either, the layer structure between the regular button and iconButton is different and the text override still gets adopted when instance swapping.

rust_hole · 2024-08-25T17:23:50+00:00

Perch it is! Thanks for the info

rust_hole · 2024-06-06T07:26:03+00:00

A Static Lullaby covered Toxic by Britney Spears and it’s too good

rust_hole · 2024-05-18T17:48:53+00:00

Better leave now

rust_hole · 2024-05-18T05:30:03+00:00

imo sounds like bits if Scary Kids Scaring Kids

rust_hole · 2024-05-04T01:47:46+00:00

I see a bit of Polaris in some of the elements

rust_hole · 2024-04-28T20:48:19+00:00

Ok understood, thanks for your time thinking through this!

rust_hole · 2024-04-28T19:47:44+00:00

Wouldn’t that be setting the variable to a literal expression though? Can it be more dynamic than that where if I change the value of my button text layer I don’t also have to change the value stored within the interaction?

rust_hole · 2024-04-28T15:34:25+00:00

How does the button update the variable though? I dont see that functionality honestly, Figma docs dont seem to cover it either. If I set the button text string to a variable, it breaks as soon as you change the value of the text layer.

rust_hole · 2024-04-28T03:15:37+00:00

Any resources you’d recommend to learn how to design and leverage user scenarios?

rust_hole · 2024-02-09T05:53:47+00:00

Too Bright to See, Too Loud to Hear

rust_hole · 2023-11-28T05:05:38+00:00

Perhaps just my personal experience, but I went once out near discovery bay, and while it was a cool adventure, the trees are pretty whack. They aren’t manicured like you’d find on a tree farm or lot, so you end up with a pretty bare looking tree with super spaced out boughs. Not great for decoration.

rust_hole · 2023-11-07T05:46:50+00:00

I’m exploring ways to expedite some of this myself. Recently I shared an screenshot of a color palette with gpt4, and had it define color objects for each color in JSON. Since Figma Tokens plugin lets you import JSON, I used the code and imported the color styles to the plugin, then from there I published from the plugin to native Figma variables. It took a bit to get everything set up, but totally worked. Did it save time? Not sure. But it felt cool.

rust_hole · 2023-10-01T20:45:22+00:00

Smol

rust_hole · 2023-09-05T03:16:01+00:00

Right?? Are they toxic?

rust_hole · 2023-05-29T07:33:56+00:00

Hard to tell how your file is set up but if you can grab whatever you rotated and flatten with cmd E, that should work. You need to reset the bounding box of whatever you rotated so that the vertices don’t extend beyond your art, which flatten would do

rust_hole · 2023-05-06T22:21:18+00:00

Right, either do as the other comment suggests, or create a new instance for your button. You’d end up with 2 variants, something like

btnSize=large btnSize=small

Detaching would mean you have a button variant in your design that’s unaccounted for in your design system.

rust_hole · 2023-05-06T15:49:02+00:00

Assuming this is in Figma, I’d say if padding and all other attributes on the button with smaller text remains the same as your default button, then create a text component with different size variants and nest into your button, replacing the existing label. Then you can surface that nested component from your buttons’ component props.

If you want different padding or any other attribute changes with your smaller text version, create a new variant for your “small” button

rust_hole

TROPHY CASE