Settings and activity
6 results found
-
36 votes
An error occurred while saving the comment 
Jeremy Mcleod
supported this idea
·
-
87 votesJeremy Mcleod
supported this idea
·
-
1 vote
An error occurred while saving the comment Jeremy Mcleod
commented
I strongly disagree with removing this, as it's something I use all the time. Maybe just change the default?
-
10 votes
An error occurred while saving the comment Jeremy Mcleod
commented
I wholeheartedly agree. It would be incredibly useful if a link target could specify both an artboard AND the desired state for that artboard. For example, I have one menu component with a different state for each potential category that might be showing. If I could make a link that specified that I want to go to THIS artboard with THAT menu category showing, it would drastically reduce the number of extra artboards I need to create.
Jeremy Mcleod
supported this idea
·
-
65 votes
Since some of you have mentioned wanting this for baseline grids, you might want to upvote this one (Baseline Grids) as well: https://adobexd.uservoice.com/forums/353007/suggestions/13030764
An error occurred while saving the comment Jeremy Mcleod
commented
You could make your grid implementation SO MUCH BETTER if you simply treated each grid as an independent layer with its own customizable properties. By default there should be no grids under the "grid" heading, but there should be a "+" button. Click that button, and it asks you which type of grid you'd like to create: layout or square, and have basic customization options for each: color, size, gutters, margins, etc depending on the selected type. Hit "ok", and now your grids list has that grid listed. You can toggle grids on and off or delete them entirely from the list itself, or you can double-click a grid to modify its configuration options. That way people could have as many layout and/or square grids as they want on each artboard.
-
2,013 votesJeremy Mcleod
supported this idea
·
An error occurred while saving the comment Jeremy Mcleod
commented
Erkan Ogumsogutlu oh no! We wouldn't want to mess up the look of the appearance panel by adding useful tools and controls, would we? Seriously, what kind of ridiculous objection is that?
Adobe, this feature is required NOW. Not only do we need explicit controls for each side of a border, being able to set independent border radii is also a mysteriously missing feature. Meanwhile, Fireworks (which you killed off in favor of XD) had independent border & border-radius controls for each side TWO DECADES AGO.
I cannot emphasize enough how terrible the current state of component states is. For example I have what I think of as a relatively simple menu. It has six different sections, and a dropdown where you pick the section. There are states for each section being active (which shows a different list of links and changes the header) and a state for each section with the dropdown open, for a total of 12 states.
You know how long it takes my seriously beefy computer to change between states on an instance of that menu? ONE HUNDRED AND FORTY SECONDS. That's just madness! Not only that, on a full navigational mockup, with 30+ instances of that component, XD will at some point wind up using almost TWENTY GIGABYTES of RAM. Again, that is madness! There is no reason for components to be as performance heavy as they are right now. I know Adobe has a ton of amazing talent; it's time to focus that talent on figuring out how to fix this feature.