Settings and activity
16 results found
-
213 votes
Apologies! I sent the Email to the wrong ticket.
Anonymous supported this idea · -
956 votesAnonymous supported this idea ·
-
1,472 votesfeature-under-review · 342 comments · Adobe XD: Feature Requests (Read-Only) » 01 : Design mode · Admin →
An error occurred while saving the comment Anonymous supported this idea · -
322 votesfeature-started · 51 comments · Adobe XD: Feature Requests (Read-Only) » 07 : Integration with other tools · Admin →Anonymous supported this idea ·
-
77 votesAnonymous supported this idea ·
-
41 votes
An error occurred while saving the comment Anonymous commentedYES THIS. I can't tell you how many times I've wanted to be able to do this.
Anonymous supported this idea · -
256 votesAnonymous supported this idea ·
-
1,728 votesAnonymous supported this idea ·
-
567 votesfeature-under-review · 138 comments · Adobe XD: Feature Requests (Read-Only) » 02 : Prototype mode · Admin →Anonymous supported this idea ·
An error occurred while saving the comment Anonymous commentedExample scenario:
I have 2 documents:
- a library file/design system
- project file 1I have imported the assets and components from my library file into the project file. I reuse a particular button (a linked component) many times throughout the project file.
Now when I go to prototype: all instances of the button in the project file should be prototype linked to the same artboard. Because my "master" component is technically the one in the library file, I can't include the prototype link as part of the component. This means I have to set up a separate prototype link for each instance of the button, even though they all go to the same place.
So we had this idea that maybe one instance of the linked asset could be the "local" master - aka it is the master only for the specific file it is in. This would allow all instances of the button to still be linked to the asset in the source file, but also allow you to set up a prototype link on the local master that would apply automatically to each child instance of the component within that same file.
I realize there could be various problems with this - such as clashes between updates made to the linked asset in the source file vs the local master. I think keeping things in this hierarchy would work:
Changes made to the source file master > changes made to the local master > overrides to the local child components
There are probably things I haven't thought of but it's just a thought! Hopefully some of it makes sense. Thanks for reading!
-
73 votesAnonymous supported this idea ·
-
5,424 votesAnonymous supported this idea ·
-
173 votes
Got it. Currently, that’s expected behavior, as double clicking and adding points converts it from a rectangle (which will maintain the corner radius) to a path, which has a different set of rules for resizing (for things like icons). I think what you want is this behavior: https://adobexd.uservoice.com/forums/353007/suggestions/12962355. If this looks good, I’ll go ahead and merge this story with that one.
-Elaine
Anonymous supported this idea · -
180 votesAnonymous supported this idea ·
-
3,888 votesfeature-in-the-backlog · 527 comments · Adobe XD: Feature Requests (Read-Only) » 01 : Design mode · Admin →Anonymous supported this idea ·
-
1,421 votes
We’re planning to support pages in XD. Stay tuned!
Anonymous supported this idea · -
67 votesAnonymous supported this idea ·
This drives me insane with hover states! Especially if it's a component that is repeated 10 or 20 times (such as a row in a table). Having to make each text change (or whatever) twice due to the hover state is extremely tedious. Thanks for looking at this one Adobe!