Bryce Flynn
My feedback
-
1 voteBryce Flynn
shared this idea
·
-
400 votesfeature-under-review · 22 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Bryce Flynn
supported this idea
·
-
449 votesfeature-under-review · 26 comments · Adobe XD: Feature Requests » 03 : Sharing on the web · Flag idea as inappropriate… · Admin →Bryce Flynn
supported this idea
·
-
505 votesfeature-under-review · 35 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Bryce Flynn
supported this idea
·
-
509 votesfeature-in-the-backlog · 43 comments · Adobe XD: Feature Requests » 07 : Mobile (iOS) · Flag idea as inappropriate… · Admin →Bryce Flynn
supported this idea
·
-
49 votesBryce Flynn
supported this idea
·
-
16 votesBryce Flynn
supported this idea
·
-
3 votesfeature-under-review · 0 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Bryce Flynn
supported this idea
·
-
6 votesBryce Flynn
supported this idea
·
-
214 votesBryce Flynn
supported this idea
·
-
4 votesbug-investigation-in-progress ·
AdminNina Ramos (Adobe XD)
(Program Manager, Quality, Adobe)
responded
Thanks for the update Ro. Sincerely appreciate you sharing detailed observations.
It sounds like you’ve found a way to make this work for you. Can you confirm? Or do you find your still blocked?
Cheers!
NinaBryce Flynn
commented
This sounds somewhat similar to the bugs in components that broke multiple symbols when they auto-updated in my mocks, resulting in hours of additional labor and the pain ain't done yet. Shouldnt have to find workarounds. Until components were 100% compatible with symbols (and they are not) Adobe should have rolled them out whilst preserving symbols.
Bryce Flynn
supported this idea
·
-
16 votesBryce Flynn
supported this idea
·
-
24 votesBryce Flynn
supported this idea
·
-
2,031 votesfeature-in-the-backlog · 265 comments · Adobe XD: Feature Requests » Other · Flag idea as inappropriate… · Admin →Bryce Flynn
supported this idea
·
-
3,939 votesfeature-under-review · 352 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Bryce Flynn
supported this idea
·
-
5,391 votesfeature-started · 294 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Bryce Flynn
supported this idea
·
-
5,992 votes362 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
Reopening the feature request, based on feedback.
Bryce Flynn
supported this idea
·
-
8,128 votesfeature-started · 936 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Bryce Flynn
supported this idea
·
-
19 votes
Hi Jan,
Thanks for your reply. Apologies if I was unclear – I didn’t mean to say that all your nested components must be master components, but to demonstrate that if you are editing master components, the edits will propagate to the other instances.
So in the original example you posted, you were actually overriding the fill color in a nested instance (not a master component). If instead, you right-clicked on the nested instance and chose ‘Edit Master Component’, your viewport would have panned to the master component, and then any changes you made to the master component would propagate to its instances. It doesn’t matter if the instance is nested in another component or not.
So nested components are fully supported in this new master/instance model, but the important thing to remember is you must edit the master component, either directly in the parent component or by right-clicking on…
Bryce Flynn
supported this idea
·
-
5 votesBryce Flynn
supported this idea
·
Often, I want to swap out a single instance of a symbol. Much less often do I want to perform a blanket swap.