New and returning users may sign in

We're glad you're here

Please sign in to leave feedback

Signed in as (Sign out)
Close
Close
← Adobe XD: Feature Requests

Request details

Feedback

Adobe XD: Feature Requests: 01 : Design mode

Categories

  • CATEGORIES
  • All ideas
  • My feedback
  • 01 : Design mode 1365 ideas
  • 02 : Prototype mode 369 ideas
  • 03: Share mode 50 ideas
  • 04 : Sharing on the web 214 ideas
  • 05 : Asset exporting 157 ideas
  • 06 : Extensibility 38 ideas
  • 07 : Integration with other tools 118 ideas
  • 08 : Mobile (iOS) 25 ideas
  • 09 : Mobile (Android) 19 ideas
  • 10: Developer Handoff 139 ideas
  • 11: Plugins 135 ideas
  • Other 109 ideas

(thinking…)
  • Searching…

    No results.

    Clear search results
    • Adobe XD: Feature Requests 2,865 ideas

Create new main component from existing component

◆ Overview
After releasing "State" feature, it's been able to prepare complex interactions like "hover." Following feature may help to reduce required time preparing a new component with similar behaviors/instructions.

◆ Actual
New component with state settings every time when a similar behavior is expected in different look and feel.
(Currently, preparing another XD file is believed to be the only solution to avoid this by selecting "Make it as local component" after loading it from another XD file.")

◆ Expected
By select "Use it as a new Master Component" is to make a new Master component instead of copying it as an instance component.

◆ Why is this valuable to you?
When using a single, new XD file and load a master component from other XD files, it is possible to make it "local component"; however, it is unable to make it happen within the same XD file.

This helps to reduce time to prepare a set of basic state setting from the beginning each time. This also helps NOT to get affected unconsciously on the new component by editing the template master component by someone else.

Since Co-Editing feature is now beta version, some larger project may have a couple of co-editors of components on the same XD file in the future. While a group of designers keeps upgrading a basic behaviors for future use, another group of designers is working on on-going project to finalize a specific look and feel based on the template component.

  •  
    Screen Shot 2019-11-07 at 8.04.39 PM.png 329 KB
671 votes

We're glad you're here

Please sign in to leave feedback

Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Kei ™ shared this idea  ·  November 16, 2019  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →

How important is this to you?

We're glad you're here

Please sign in to leave feedback

Signed in as (Sign out)
Close
Close
Tweet
  • Remove
Attach a File

We're glad you're here

Please sign in to leave feedback

Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Nándor János Danyi commented  ·  February 25, 2021 00:12  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Hi,

    +10000 votes for this feature.
    Everything on the asset panel should be duplicatable and mergeable.

    Submitting...
  • Chris K. commented  ·  February 24, 2021 20:45  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    This is sorely needed. I think it would be super easy to implement too. Just add a new menu item when you right-click on an instance that converts it to a new main component.

    I can’t tell you how many times I’ve had to create new components from scratch that were very similar to other components I had already created. I did not know about the work-around, so that helps a ton, but this is an easy, much-needed feature.

    Submitting...
  • Laurel commented  ·  February 22, 2021 11:27  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    I thought I was working on 5 Main components. And after making all my edits, realized they were all "Instance" not "Main" because I'd saved the document under a new name. So now none of my component changes rippled through the document! If I ungroup the components, I will lose my hover states.

    So YES. We need the capability to change an Instance of a component to either override the main, or be a new component, with all states inherited.

    Submitting...
  • René Kostka commented  ·  February 18, 2021 06:57  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Thanks Vlad, this is a great workaround! Especially for complex components with many states.

    For others who'll try Vlad's way: After pasting back and making local you need to also click Edit main component (because the pasted one is an Instance).

    Submitting...
  • Vlad Iepure commented  ·  February 11, 2021 07:44  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    A quick workaround for duplicating components with a lot of similarities:

    Copy/paste component in another file, then make local to that file and rename.
    Then copy/paste back the new renamed component to your file and make it local again.

    This seems to me, to be faster than rebuilding the component from scratch.
    Cheers

    Submitting...
  • Vlad Iepure commented  ·  February 11, 2021 07:37  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    This is very much needed for building any complex design.
    Thanks

    Submitting...
  • Vincent Young commented  ·  February 09, 2021 16:44  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Please implement!

    Submitting...
  • Gustavo commented  ·  February 05, 2021 04:32  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    It's been way too long without this...

    Submitting...
  • Matthew Prina commented  ·  February 02, 2021 10:04  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    I've voted for the "Duplicate Master Component" feature but I like this too because it would be cool to create a master (main) component from an instance of a component.

    Think about it. You design a component that you're using a lot and in one instance you notice that the component needs some improvements. You make the necessary improvements to that instance. Now you decide you want all the components to look/function like that instance. If you could have the option to 1."make new main component from this instance" and 2."make this instance the main component" - it would be super helpful.

    Submitting...
  • Matt Prina commented  ·  February 02, 2021 09:54  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    This would be a great improvement. I find myself wanting to do this all the time. It would save a lot of time.

    Submitting...
  • Mee K commented  ·  January 27, 2021 00:01  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Make it please. It's too annoying to copy it now.
    1. Create a new file
    2. Copy Components
    3. Rename, re-copy and paste into the original file.
    4. Delete and close saved files in the cloud
    This process must be completed with only one button.

    When someone asks me about that, I say, "Well, it's a little annoying, but try like this! blabla... ", What a hassle!

    Submitting...
  • Anonymous commented  ·  January 22, 2021 14:37  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Please, desperately need.

    Submitting...
  • fcairello commented  ·  January 20, 2021 22:43  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Also came here expecting to find an answer to this problem, and ended up disappointed because I see that Adobe hasn't implemented the functionality to create a master component from an instance component yet, even though people has been asking for it since two years ago. This would be indeed very useful and I am just another example who really needs it as well. It seems like Adobe doesn't have people working on real life projects who could realize what are the little and simple improvements they could do that would greatly facilitate the designers work, what a shame.

    Submitting...
  • Lawrence Alberto commented  ·  January 06, 2021 16:19  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    I wish they make this a priority as it will cut a lot of tedious work when setting up main components.

    Submitting...
  • Noel Holmes commented  ·  January 04, 2021 11:59  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Would be especially useful for creating variations of masters that have different states defined!

    Submitting...
  • Riccardo commented  ·  December 16, 2020 06:06  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    it's a really basic and useful feature, possibility to create a new "master" component instead of unlink and recreate all state from scratch

    Submitting...
  • Mike M commented  ·  December 10, 2020 12:28  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    This is needed so badly. It's super annoying and tedious to have to make multiple versions and alterations of an instance component for states and interactions to show clients, and when an option is chosen, we have to go and re-create the one chosen if it's not the master component.

    Submitting...
  • Laurel commented  ·  December 08, 2020 15:25  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    It's insanity that we can't do this.

    I just made 6 states. Then realized I need 6 individual components instead so that each "state" can have an independent trigger. If we could duplicate master components, then I would be able to duplicate, rename, and delete the superfluous states.

    You are probably adding 2-3 hours of work to my day but not having this simple feature. And this happens to me all the time.

    Submitting...
  • Patrick commented  ·  December 01, 2020 02:11  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    PLEEEEAAASE! The lack of this feature is driving me crazy!

    Submitting...
  • Anonymous commented  ·  November 30, 2020 10:06  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Yes Please!! I spend so much time dealing with visuals independently because of this issue

    Submitting...
← Previous 1 2 3 4 5 6 7 Next →

Adobe XD Feedback : Feature Requests & Bugs · UserVoice Terms of Service & Privacy Policy · Adobe Terms of Use · Adobe Privacy Policy