Rearrange Component States in Property Inspector
I'd love to be able to rearrange the component state order in the property inspector (the panel on the right in Design mode & Prototype mode). I would also love to be able to resize the section for component states. Currently it maxes out at 4 before you need to scroll.
Kim Langenkrans commented
Nick Morgan commented
This would be a major workflow improvement for any designer or team that manages their components in a complex way. The Layer and Libraries panels both have this ability, so I would think this could be addressed more easily than other requests. I'm not a developer though, so some development challenges may exist that I'm unaware of.
My biggest issue with the lack of this feature, is that you have to strategically create component states in order for them to be displayed in your desired order.
When a designer needs to create new component state in the future, the new component state is only added to the bottom of the list, and can not be grouped with other similar components that might be higher up in the list.
I hope that Adobe pursues feedback requests independent of their popularity, especially since the request list default sort order is by popularity. This request, for example, is on page 9, but is much more basic functionality than quite a bit of the more popular requests. Just my opinion, but it looks like it's shared with many folks on this thread.
While we are at it, perhaps moving the component panel into the left side would create the additional benefit of resizing width as well. My component state names are wider than the allotted window width of the component state list in the properties panel.
Alright, coffee is wearing off, I'll stop here... :)
Milan Manojlovic commented
Its not idea. Its bad UX in here. I can't see all my states in one bite. Without any reason states view masking my states list.
Yo! Option to rearrange component states! NOW!
Pretty please...! Thank you!
Totally agree on this. I recently switched from Sketch and I love XD but this seems like a serious oversight.
This seems mandatory. I have 10 states on certain components, for example making a tabbed section. I'd like to reorder the states into a logical order.
Seriously, how is this not a thing yet? Even if the MVP is alpha sorting them for now and adding reordering feature later that would be fine. Either way not including some form of sort by default is a complete misstep.
For further clarification on the last bit of this request, the component section is way too small. See attached, simply make the section at least half the prototype panel.
Also would be nice if it didn't hide the states when I have a interaction trigger selected, just keep both visible.
This is a complete and utter embarrassment for XD in terms of components. This needs to be added so that design systems and component libraries can feel organized and not amateur.
Marlin Prauss commented
I really miss the feature to rearrange the states of components. sometimes one simply needs to change the order.
Flavio Mauri commented
Yes! I just posted this on twitter a couple days ago. I don't see any reason why not, surely this aspect needs to keep up with evolving necessities of the designer, whom might think or receive request to implement new states at a later date, but that would be convenient to keep in a certain hierachy
Gino Rodrigues commented
Components with many states often require some logical clustering in the list, otherwise it may get really confusing.
I've been "provisioning" many empty states ahear, only to try to control the order of the list, but a simple drag would be way simpler.
Christoph Leitner commented
Rearranging would be very helpful. Currently it is a lot of work to fix a bad arrangement in a component with a lot of states. Resizing the section would also be handy - picking the right state out of list with 16 states makes me uncomfortable now.
I was creating states and I identified the necessity to create a state between others two. I tried to drag the new state but it didn't have any effect.
It would be cool if we were able to reorder states
Tyson Reeder commented
This is much needed. If you don't plan carefully your states will be in a not ideal order with no way to rearrange the items without releasing the component and starting over.
Warren Wang commented
I think on top of being able to rearrange them, it would be great to be able to make groups as well. I'm trying to sort a style guide right now and it'd be great if I could get all my button permutations into one master component. Right now without this it's a mess.
Just to clarify, this post is about the ability to rearrange the component states in the Property Inspector > Component section (the panel on the right in Design mode and Prototype mode). Thanks.
Component state are great. However this is one of the features that is sorely needed now that we have states. Input and button states are a good examples of how organization of multiple states really matters. For instance, in an input I could need an input without a label or with a label, and without helper text or with help text, and need to show each of these in default, focus, error, and disabled states. Additionally, I made want to add or remove the required tag as needed.
One could argue that I could simply make 4-8 separate master components. However, if the intent is of the program is rapid prototyping, and I believe the intent of states is to improve this by not having to create repeat components that are, for all intent and purposes, closely related at the atomic level. The examples provided are additional artifacts that modify an atom (the most basic usable element), they are not atoms themselves.
I would not expect all sizes of each atomic element to be kept in state. However, there is not reason to consider this as well. I think the general idea is to keep your components tab as clean as possible. Particularly if an organization is trying to drive their design governance, in part, through XD.
Something as simple as not being able to reorder these makes the state less useful and, in some cases, causes outright confusion when consumed by those that did not create the component and it's corresponding states.