Michael
My feedback
-
56 votesfeature-under-review · 12 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Michael
supported this idea
·
-
740 votesMichael
supported this idea
·
-
1,524 votes273 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Michael
supported this idea
·
-
42 votes
With the XD 26 release, padding is available on any group, configurable in the layout section.
Learn more here: https://helpx.adobe.com/xd/help/set-fixed-padding-for-components-groups.html
The spacing functionality is also coming soon.
Best regards,
AndreiMichael
supported this idea
·
-
46 votesMichael
supported this idea
·
-
921 votes102 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Michael
supported this idea
·
-
152 votesMichael
supported this idea
·
-
147 votes19 comments · Adobe XD: Feature Requests » 07 : Integration with other tools · Flag idea as inappropriate… · Admin →
We have a story to fix this and give a preview of an artboard for this view.
Michael
supported this idea
·
-
18 votesMichael
shared this idea
·
-
17 votesMichael
commented
I agree, as I am also having the same frustration going from XD to Sketch, but I would expand this to "Copying vector objects from XD should copy vectors to the clipboard".
Even copying a vector shape from XD to Adobe Illustrator results in a bitmap image being pasted into AI. Whereas copy and paste from AI to XD works perfectly. Apparently XD does not support copying vectors to the clipboard in a way that can be used outside the app. The AI aspect is addressed here: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/13118382-copy-from-xd-paste-into-illustrator-or-photosho
...But I would like to see a vector clipboard format that would allow copy and paste to both AI and XD (since they are already compatible with each other), and thus deal with both issues at once.
Michael
supported this idea
·
-
1,211 votes259 comments · Adobe XD: Feature Requests » 05 : Asset exporting · Flag idea as inappropriate… · Admin →Michael
supported this idea
·
-
6,134 votesfeature-started · 329 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Michael
supported this idea
·
-
238 votes40 comments · Adobe XD: Feature Requests » 07 : Integration with other tools · Flag idea as inappropriate… · Admin →Michael
supported this idea
·
-
91 votesMichael
supported this idea
·
-
23 votes
You can currently add an object to a symbol by cutting, selecting an object inside the symbol, and then pasting. You can also enter and exit group edit context really quickly by double clicking on a symbol or group. However, you’re right in that you currently can’t drag directly into a symbol. I’ll repurpose this request to focus on that behavior.
-Elaine
Michael
commented
Fellype, copy and paste worked for me, to insert an item into a symbol. (The paste step may not be visually obvious, because XD pastes the item over the original item it was copied from, instead of into the symbol's general location. But if you look in the layers panel, you should see that the item has been pasted into the symbol group.) Are you using the latest version of XD?
Michael
commented
Thanks, Elaine. Appreciate the tip (copy and paste), and editing the suggestion to specify the issue.
Michael
shared this idea
·
-
235 votesMichael
supported this idea
·
-
6,629 votes385 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
Reopening the feature request, based on feedback.
Michael
supported this idea
·
-
174 votesMichael
supported this idea
·
A quick improvement would be to enhance the global color assets so that when those colors are changed, the same colors in the Saved Color Swatches are also changed. Currently editing the global colors changes them throughout the document, but not in the swatches panel … which is frustrating. The swatches must be manually deleted and recreated. Given that the swatches are document-specific, there seems to be no good reason for this.