Martin Klausen
My feedback
-
34 votes10 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
-
3 votes
-
5 votes3 comments · Adobe XD: Feature Requests » 04 : Sharing on the web · Flag idea as inappropriate… · Admin →
-
303 votes
-
71 votes
-
204 votes40 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
As a workaround for this featire you can make your home artboard an “index” page which links to the different views/subsets of your design. When you share your design and visit the URL you can click through to the real home artboards and copy the URL (each artboard has it’s own URL on the shared link). You can then share these URLs to link people to a subset of your design.
We hope to be able to formalize this feature in the future.
+1
My use case:
I have a file with multiple flows unrelated to each other. When a feature is completed and ready to send to a developer I need to select a new Home artboard so the team can see the latest flow. But this takes away the link to all the other flows.The workaround works ok for now.
-
22 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…
+1
-
18 votesfeature-under-review · 1 comment · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →
-
18 votes
-
412 votesfeature-under-review · 124 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
-
5 votesbug-needs-more-info · 6 comments · Adobe XD: Bugs (Read-Only) » Prototype · Flag idea as inappropriate… · Admin →
Reading the comments i figured it out. You cant select the wire, you need to select the element itself. It's a bit weird that its disabled, i think this could be improved.
-
1 votebug-needs-more-info · 3 comments · Adobe XD: Bugs (Read-Only) · Flag idea as inappropriate… · Admin →
Have attached file here
I have the same problem in v22.0.12.12
-
4 votes
I think the design tool that can solve this will be the winner
-
17 votes
-
19 votes
-
126 votes21 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
-
151 votes
-
174 votes8 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
-
7 votes
+1
I also find this a bit backwards from how symbols worked. Loved how you would always iterate on symbols in context but now you are taken off canvas which also forces you to scroll back cause you loose context. Wish it would be possible (made simpler) also with components.I guess that’s the only thing I miss from the symbols era.
-
1 votebug-investigation-in-progress ·
AdminNina Ramos (Adobe XD)
(Program Manager, Quality, Adobe)
responded
Hello! The team has released an update XD 19.1 which may address this issue.
Can you please update and report back if that helps?
Thanks!
NinaHello XD team, this works for me now!
Im on version 20.1.12.4.
Thanks :)
I still have the same issue after updating XD :/
+1
I've got a file with design layout + design system components in the same file. Now that the project has grown I would like to relocate the design system components (not all components) to a separate file.