Settings and activity
7 results found
-
8,057 votes
Reopening the feature request, based on feedback.
Rick Bond
supported this idea
·
-
Stacks should dynamically shift content in Preview
-
Screenshot 2022-01-14 at 12.55.47.png 233 KB -
Stacked components.mp4 641 KB -
interactive-layout.gif 325 KB -
design-mode.gif 657 KB -
prototype-mode.gif 250 KB -
Expanded-Prototype.png 30 KB -
Expanded-Design.png 98 KB -
Adobe XD State Change Padding Feature Request— August 25, 12.21.06 PM.xd 104 KB -
XD Issue.mp4 3480 KB -
2020-06-18 01-27-01.mp4 2266 KB -
Link components.png 58 KB -
Components.png 18 KB -
Components stick.png 30 KB
313 votesPlease note that stacks is a feature that is intended to be used at design time, and does not dynamically shift the stack in preview. I’m going to rewrite this particular request to be more precisely about the latter suggestion.
An error occurred while saving the comment Rick Bond
supported this idea
·
-
-
37 votesRick Bond
supported this idea
·
-
39 votesRick Bond
supported this idea
·
-
694 votes
An error occurred while saving the comment Rick Bond
commented
Thank you for this. I suggest that the Adobe Xd dev team look at Adobe Illustrator > Scale Strokes and Effects preference as it does exactly what the OP and I need *I think*
Rick Bond
supported this idea
·
-
1,540 votes
We announced CC Spaces in XD today at Adobe MAX! In a space, all members will be able to publish a link. More details to come!
An error occurred while saving the comment Rick Bond
commented
Relates / duplicate of this issue with 160 votes of it's own. https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/38308750-change-owner-of-cloud-document
Rick Bond
supported this idea
·
-
994 votes
We announced CC Spaces in XD today at Adobe MAX! In a space, all members will share ownership of the document, which means people leaving an organization won’t impact your workflow. More details to come!
Rick Bond
supported this idea
·
tl;dr I'd like to suggest that users be better informed in-app that stacks is a design only feature, to set realistic expectations and avoid user frustration and waste. Until stacks work in preview, only use them for basic layout - nothing nested.
Just adding my 2 cents. I work as a UX designer as part of a large enterprise UX team and have observed 2 team members losing DAYS of work because there was no indication when using stacks to design, (SUPER USEFUL FEATURE in design mode, we all LOVE it!!!)
Well, after mocking up a complicated nav using stacks, they discovered that it didn't render as expected in preview. Their work ended up being thrown away because it not only doesn't work in preview... It breaks it. Any stacks then need to be recreated the good ol' manual way. Fine, just time consuming. And if I hadn't been made aware by my colleagues I very well would have fallen into this same "trap" myself.