Settings and activity
12 results found
-
134 votes
Robert Anderson
supported this idea
·
-
149 votes
This is something we’d like to get more feedback on.
a) Some apps (such as Adobe Illustrator and InDesign) behave the way XD does now: reducing fill opacity (not overall object opacity) keeps the whole shadow visible but reduces its opacity in proportion with the fill color’s opacity. At zero fill opacity, the shadow is completely gone along with the fill (unless you have a border, in which case you have a thin ring-shaped shadow left).
b) Other apps (such as Photoshop or Sketch) behave differently: reducing fill opacity leaves the shadow’s opacity at full strength, but clips the shadow so you don’t see it through the translucent fill. At zero fill opacity, in the middle of the shape you can see what’s behind it completely unobscured, but outside the shape’s edges you still see the drop shadow at full strength.
Which one do people prefer? Do you need to…
An error occurred while saving the comment Robert Anderson
supported this idea
·
-
237 votesRobert Anderson
supported this idea
·
-
639 votes
Hi everyone,
We’ve started working on multiple fills and borders, with plans to extend to this multiple shadows in the future.
Best,
DanRobert Anderson
supported this idea
·
An error occurred while saving the comment Robert Anderson
commented
How does it take Adobe over a year to implement something that they already do in a lot of their other apps? Doesn't "feature started" mean that you've actually started working on it? I definitely understand that development takes time, but if it's taking this long I start to doubt the ability of your team, or the meaning of the label "feature started". Please be honest with us, if you had to put it on hold, tell us so we aren't anxiously waiting for a feature that you're not working on.
-
2,719 votesfeature-under-review · 108 comments · Adobe XD: Feature Requests (Read-Only) » 02 : Prototype mode · Admin →
An error occurred while saving the comment Robert Anderson
commented
The "drag" feature does account for some of the use cases, but I haven't been able to figure out how to drag in multiple directions to trigger different transitions. For example, I have a table row, and I want to swipe left to delete, and swipe right to flag, I am only able to have one drag transition, and therefore I can only do one of these actions. Drag doesn't indicate direction either, it could mean along the x or y axis or both. swipe is a standard term that is used to indicate a type of gesture, and also allows the context of direction (ie. swipe left, swipe right, swipe up, and swipe down) that allows up to 4 different gestures and therefore 4 separate interactions or transitions, rather than the 1 that is provided with a "universal" drag. I hope this feature does get implemented soon as I have always loved the idea of XD, but have found that it has always had some holes in the execution that prevents it from actually being the best platform on the market.
Robert Anderson
supported this idea
·
-
260 votes
An error occurred while saving the comment Robert Anderson
commented
the context aware layers panel does a great job of allowing me to see what's important (including locked layers on the artboard I'm working on) Not being able to drag to select just what I want, is killing me. I work on projects that need backgrounds with overlays, and it's very frustrating to have to try and deselect those locked backgrounds. Why would I even lock it if it's going to be selected... can't understand this
Robert Anderson
supported this idea
·
-
1,728 votesRobert Anderson
supported this idea
·
-
193 votesRobert Anderson
supported this idea
·
-
27 votesRobert Anderson
supported this idea
·
-
8,056 votes
Reopening the feature request, based on feedback.
Robert Anderson
supported this idea
·
-
1,115 votesRobert Anderson
supported this idea
·
-
704 votesRobert Anderson
supported this idea
·
option B is a must, but like others have said, if we could do both easily, even better