Settings and activity
27 results found
-
3 votes
plainclothes
shared this idea
·
-
70 votes
An error occurred while saving the comment plainclothes
supported this idea
·
-
37 votesplainclothes
supported this idea
·
-
167 votesplainclothes
supported this idea
·
-
21 votesplainclothes
supported this idea
·
An error occurred while saving the comment plainclothes
commented
This is closely related to actually finishing the basic cross-state inheritance as described in the issue below and elsewhere.
https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/41922067-keep-elements-properties-between-states-propagateOnce inheritance is solved in a useful way, the ability to opt elements out of inheritance would be a useful enhancement.
As it stands, components are really just a dangerous distraction. For a project of any size and complexity, you'll be better off communicating states some other way until the XD team finishes this feature.
-
213 votes
Apologies! I sent the Email to the wrong ticket.
plainclothes
supported this idea
·
An error occurred while saving the comment plainclothes
commented
Wow -- that Flash reference brought back some painful memories!
-
1 voteplainclothes
shared this idea
·
-
32 votesfeature-under-review · 5 comments · Adobe XD: Feature Requests (Read-Only) » 01 : Design mode · Admin →
An error occurred while saving the comment plainclothes
commented
This is a silly little thing. Why do I have to break the grouping of a component to unlink it from the master? Just disconnect / detach it and leave the grouping in place.
plainclothes
supported this idea
·
-
134 votesplainclothes
supported this idea
·
-
2 votes
An error occurred while saving the comment plainclothes
commented
I need the ability to have more than one layout grid in my documents.
Rather than setting one as the default, I should be able to define a grid, give it a name, then select it again from other boards.
Ideally, these layout presets could be loaded into other documents as well (but higher order than a library asset).
plainclothes
supported this idea
·
-
956 votes
An error occurred while saving the comment plainclothes
commented
Just to clarify, there are two features needed here:
1. Nested components can trigger a state change in the parent component
2. One component can trigger a state change in another, unrelated component on the same artboardThe super feature would be …
A component can trigger an artboard transition *and* change the state of a component on that artboard.plainclothes
supported this idea
·
-
9 votes
An error occurred while saving the comment plainclothes
commented
My scenario is very similar to the OP's.
To make XD even remotely usable, I have to break the app into separate flows. Even in this limited mode, a normal flow for me has 20-30 artboards. XD's flow upload is understandably slow, considering the number of interactions I usually am including.
Even with only a couple of dozen artboards per flow or less, selective upload to the parent flow (as other apps have implemented) would be a big productivity boost for me.
Related to the OP's last point, I might also have sections of a flow that aren't quite ready for my dev team. In those cases, I'll post a basic version first so they can see the whole flow, but I don't yet want to confuse them with enhancements that are still in-progress.
plainclothes
supported this idea
·
-
123 votesplainclothes
supported this idea
·
-
1,472 votesfeature-under-review · 342 comments · Adobe XD: Feature Requests (Read-Only) » 01 : Design mode · Admin →
An error occurred while saving the comment plainclothes
commented
This is the single most painful hole in the XD experience. I have 5 states on all my buttons and the app I'm working at the moment has a LOT of buttons. In many cases, those buttons also have a leading icon.
Multiply this by five:
1. Change the text
2. Swap the icon component
3. Recolor the icon component (because it forgets the color override)
4. Resize the icon component (because it forgets the size override)
5. Switch to the next stateComponent states are cool, but you pretty much hate them once you have a large app prototype up and running and you keep finding states you overlooked in your late night cram session.
plainclothes
supported this idea
·
-
167 votes
Sorry for the false alarm! Someone pointed out to me that I interpreted the request incorrectly. While you can now select objects both in the artboard and on the pasteboard, you cannot yet select objects on the pasteboard and complete artboards themselves.
An error occurred while saving the comment plainclothes
commented
The fixed pasteboard and lack of pages conspire to make this missing feature downright depressing.
XD seems to be intended for messy designers who have no interest in efficiency.
plainclothes
supported this idea
·
-
96 votesplainclothes
supported this idea
·
An error occurred while saving the comment plainclothes
commented
This is a big pain point for me.
Here's my scenario.#1: I don't want your cloud
I work with more than XD files (shocking, I know) and each of my projects is collected in a Git repo. I have no interest in throwing my files into Adobe's cloud, especially since it doesn't work with my other file types (code, Sketch, etc).#2: One doc doesn't have enough space for a serious app
So I end up with multiple files to make room for all the features of the app. If XD had pages, like everybody else, I'd just build one mega file … but it doesn't. I usually end up with separate documents for each major feature area. For an app with pages, I often run up to 10 to 20 pages depending on the complexity of the app. With the pain and suffering of XD, I try to keep it to 5 documents or less.#3: I'm not always connected
Sometimes I'll work from a trailer in the mountains. That's a pretty cool part of my job. But Adobe doesn't seem to think I should do that. In their eyes I'm connected or I'm not working. Okay then.All that to say …
Linking to local documents as shared libraries is table stakes for this feature. Kano says, "Basic!"
-
12 votes
An error occurred while saving the comment plainclothes
commented
This would be hugely useful.
If two long-standing feature gaps were addressed this could be done without a separate theme capability:
- One component can be based on another, complete with states
- Secondary states inherit default state changesThen you could quickly create a component based on the primary "theme", make a few style changes, and have everything else managed from the parent.
plainclothes
supported this idea
·
-
26 votesplainclothes
supported this idea
·
An error occurred while saving the comment plainclothes
commented
This is clearly a bug with the filter behavior.
Because of multiple other issues with XD, I have to ungroup repeat grids to create variations.
I inevitably make adjustments to what would have been grid items.
The only efficient way to do this (short of fixing the repeat grid feature) is to filter my layer panel and multi-select the items to move.
Of course, XD blocks me there too.I swear Adobe is trying to get me to convert all their users to Sketch.
Just fix it. Seriously, how hard can this be?
-
489 votes
An error occurred while saving the comment plainclothes
commented
I'd prefer to stack the panels … just like XD does on the right side … and every other design app has always done.
XD needs a UX designer.
plainclothes
supported this idea
·
-
One single interaction can trigger multiple actions to take place.
-
example.png 17 KB -
Zrzut ekranu 2020-10-23 o 14.49.36.png 20 KB -
Scroll to 'about' by 'tap' triger but the state is still 'default' (home) and I can't add another action to change the state on 'tap' trigger.png 54 KB -
About state by hover triger.png 63 KB -
default state.png 50 KB -
Scroll to 'about' by 'tap' triger but the state is still 'default' (home) and I can't add another action to change the state on 'tap' trigger.png 67 KB -
About state by hover triger.png 66 KB -
default state.png 65 KB
104 votesplainclothes
supported this idea
·
An error occurred while saving the comment plainclothes
commented
Here's my most common scenario:
- Button interaction triggers a modal
- Interaction with modal transitions to new view
- New view displays a confirmation overlayCurrently, that means:
- Duplicate artboard for second view with confirmation overlay as part of the layout
- Convert the content of second artboard into components (so I don't have to manage layout copies)
- Deal with a very cluttered Assets panelThe Assets panel thing would be less of an issue if XD offered any sort of organization of components 🤦♂️
Ideal scenario:
- Trigger modal on view one
- Interact with modal to transition to view two
- Same interaction with modal triggers new overlay on view two -
%20and%20I%20can't%20add%20another%20action%20to%20change%20the%20state%20on%20'tap'%20trigger.png){kind=link}
%20and%20I%20can't%20add%20another%20action%20to%20change%20the%20state%20on%20'tap'%20trigger.png){kind=link}
Save locally should, clearly, be the default.
Save to Adobe's silly and unnecessary server system should be an opt-in preference.
How about "check in to git repo"? That might actually be useful.