Settings and activity
27 results found
-
13 votes
Thanks for your feedback! UserVoice works best when you only have a single request per ticket, so I’m going to repurpose this specific ticket for the drop shadow spread. Please do feel free to file your second idea as a new ticket. Thanks!
plainclothes
supported this idea
·
-
10 votes
An error occurred while saving the comment An error occurred while saving the comment plainclothes
commented
When a component instance is selected, the inspector panel should show the master component name so I know exactly what I'm working with.
To get around the limitations of XD I have a *lot* of components. Many of these are nested. Sometimes it's hard for me to tell which version I have selected or even what level of the nested component I'm at.
Currently, the Component inspector section in the right panel tells me what states are available, which is a hint.
I can right click and ask to see the Component in my Assets panel (which doesn't work if I haven't already expanded the Assets panel 🙄).
I can also switch to the layers panel to see what the layer name is.Those are poor solutions to the problem of quickly seeing what component is currently selected. I should be able to see the name right in the component inspector.
plainclothes
supported this idea
·
-
76 votesplainclothes
supported this idea
·
An error occurred while saving the comment plainclothes
commented
Scenario:
I have a layout component where several things change based on the state of a nested toggle control.
When the toggle changes, I need the parent component's state to change.
-
737 votes
An error occurred while saving the comment plainclothes
commented
Just to clarify what I expect this to do.
- Select an existing master component (eg a button with several states)
- Create a copy of that component as a new component (eg button with leading icon)
- All states are retained in the copied component and I can edit the new versionThis would make creating variations of a primary component a breeze. Alas …
Today I have to
- Create an instance of the component
- Ungroup it (which really means unlink and ungroup, btw)
- Regroup the elements
- Turn that into a new component
- Make my small tweak
- Recreate all the statesI could also copy it to another doc, make it local there, rename and modify it, and copy it back in.
In either case, the workaround is absurd.
As has always been typical of Adobe products, Components persist as an abandoned feature while Adobe sends it's product dev team on tangents to create features to support marketing headlines.
plainclothes
supported this idea
·
-
464 votes
An error occurred while saving the comment plainclothes
commented
You've got component states and local overrides. Clearly, this behavior is expected in repeat grids as well.
This feature request has been around since the early days when I first tried to struggle my way through XD. How can this not be implemented yet?
Another "almost there" core XD feature, 6 years on.
plainclothes
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 plainclothes
commented
When developing complex app interfaces, I convert control groups (eg a set of fields) into components with various expanding states.
The whole set of components exist within a stack that might also be within a container that requires padding.
While designing, I can switch states, expanding the dimensions of a component, and the overall design will expand to accommodate the new state. This incredibly convenient for designing complex app UIs and is probably the only meaningful advantage XD has over Sketch.
My hope was that I could wire all those states together (make selection B in field 1 to expose child controls for 1.B) so a prototype could demonstrate the UI responding to interaction.
Unfortunately, all that component state work is largely wasted (outside of my own design efficiency) because the resulting prototype completely ignores stacks and padding.
If interactive prototypes supported the rules of stacks and padding, XD would have a viable place in the product design landscape.
plainclothes
supported this idea
·
-
-
3,558 votesfeature-under-review · 317 comments · Adobe XD: Feature Requests (Read-Only) » 02 : Prototype mode · Admin →plainclothes
supported this idea
·
When a component instance is selected, the inspector panel should show the master component name so I know exactly what I'm working with.
To get around the limitations of XD I have a *lot* of components. Many of these are nested. Sometimes it's hard for me to tell which version I have selected or even what level of the nested component I'm at.
Currently, the Component inspector section in the right panel tells me what states are available, which is a hint.
I can right click and ask to see the Component in my Assets panel (which doesn't work if I haven't already expanded the Assets panel 🙄).
I can also switch to the layers panel to see what the layer name is.
Those are poor solutions to the problem of quickly seeing what component is currently selected. I should be able to see the name right in the component inspector.