This is a topic that has been discussed many times (for example here) and I imagine it is something that is close to the hearts of many.
Component swapping is a bit limited in Penpot. It works great for icons or single elements; the problem arises when I need to change the state of a button for example. If I change the child of a button (for example from “button” to “click here”) and then swap to another state (for example from “active” to “hover”) the button loses any text changes made to the child and reverts to the text in the master (“button” in my example). This is very time consuming and does not allow for flexibility in the workflow.
Like you said, it’s not the first time this topic has come up. We know that this is a major shortcoming that needs to be solved.
The good news is that we are already working to solve this use case. We hope to be able to launch the improvement in the next release. This is the story.
Great! Sorry if I duplicated an existing topic but I didn’t see you working on it when I looked, but as always you are on point! Thanks for everything.
sorry for nothing! duplicated requests can have their value too, they help us to have some sort of sense of the interest level about something. In this case, it can also tell that we’re working on the right things
I’ll only add here that I’ve seen the sneak peeks and this looks really great! A bit of context; this user story also serves the upcoming Penpot Variants feature, but we were able to detach it from that release and make it available asap.
