Settings and activity
20 results found
-
834 votes
Morgan Caldbeck
supported this idea
·
-
5 votes
An error occurred while saving the comment Morgan Caldbeck
shared this idea
·
-
18 votesMorgan Caldbeck
supported this idea
·
-
1,809 votes
An error occurred while saving the comment Morgan Caldbeck
commented
We do need spell check, I agree. To some extent though you can “find and replace” text by using components. If you create a button, make that a component and then edit the text, the text on all instances of that component will change to match. Hopefully that helps!
-
Tabbed design view for multiple files
-
Multple Windows.png 731 KB -
Screen Shot 2021-01-29 at 4.14.22 PM.png 462 KB -
Screen Shot 2021-01-29 at 4.14.22 PM.png 462 KB -
Screen Shot 2020-02-27 at 10.03.53 AM.png 57 KB -
needs resizing and scrollbars.JPG 110 KB -
1 (3).png 1 KB -
1 (2).png 2 KB -
1 (1).png 66 KB -
Screen_Shot_2016-05-09_at_6.02.21_PM.png 21 KB
638 votesfeature-under-review · 117 comments · Adobe XD: Feature Requests (Read-Only) » 01 : Design mode · Admin →An error occurred while saving the comment Morgan Caldbeck
commented
This is already possible. Xd opens a launcher on startup where you can select the file you want. If you need multiple open, just pull up the launcher and select another file. Both will remain open.
I do this on my Mac frequently, and full screen each document so that switching between just requires a simple three finger swipe left or right to go to the one I want.
I’m not sure if windows version allows for all of that though. I would assume yes.
-
-
2,013 votesMorgan Caldbeck
supported this idea
·
-
1,774 votesfeature-under-review · 81 comments · Adobe XD: Feature Requests (Read-Only) » 01 : Design mode · Admin →Morgan Caldbeck
supported this idea
·
-
1,851 votesMorgan Caldbeck
supported this idea
·
-
3,558 votesfeature-under-review · 316 comments · Adobe XD: Feature Requests (Read-Only) » 02 : Prototype mode · Admin →Morgan Caldbeck
supported this idea
·
-
428 votes
I’m going to leave this one open, but please note that you can do this already using auto-animate and the time trigger.
Morgan Caldbeck
supported this idea
·
-
516 votesMorgan Caldbeck
supported this idea
·
-
956 votes
An error occurred while saving the comment Morgan Caldbeck
commented
I do agree, that we should have the ability to use a state change trigger the state of an otherwise unrelated component.
For example, when building a mega menu, I have a list of items on the left side. I want to be able to “click” that item (thus triggering a state change), and further have that change my items list on the right to a state reflecting the clicked category with its appropriate set of items.
This would allow us to create fully functional site demos.
An error occurred while saving the comment Morgan Caldbeck
commented
There is the ability to use components inside of components in different states. As of now, we can set component A to a different state, if component B is inside of A, we can set A to, for example hover state, and in design mode, with A set to hover, we can set B to a different state as well.
With this method, you can alternate states of components within other components based on the parents state.
That may be hard to understand but that’s a very brief summary of doing what your talking about here to a limited degree.
Morgan Caldbeck
supported this idea
·
-
1 voteMorgan Caldbeck
shared this idea
·
-
2,509 votes
We think you’re going to really, really dig the plugin integrations we’re making available later this year :)
Hoyle
Morgan Caldbeck
supported this idea
·
-
Dark Interface (overall UI including side panels) / Dark mode
-
Screenshot 2021-02-19 222634.png 29 KB -
Light Mode.png 351 KB -
Dark Mode.png 301 KB -
Untitled-1.jpg 229 KB -
Screen Shot 2019-12-04 at 3.11.59 AM.png 1225 KB -
Screen Shot 2019-12-04 at 3.53.41 AM.png 604 KB -
1 MacOS 10.15.2 beta Catalina.png 358 KB -
Screen_Shot_2017-09-21_at_1.02.42_PM.png 54 KB -
adobe_xd_-_plz_add_color_theme_options.png 2 KB
5,425 votesMorgan Caldbeck
supported this idea
·
-
-
488 votes
An error occurred while saving the comment Morgan Caldbeck
commented
I've been building a lot of animations prototypes lately as I've been working on some big-fidelity final passes on web applications. In my experience, auto animate has been fantastic and there are almost endless possibilities, so thank you very much for your hard work on that feature!
While it has been amazing, I think there are improvements that could be made. Currently, to use auto-animate you have to use separate artboards for each portion of the animation. This causes bloats file sizes and adds complexity to documents, especially when sharing for review and there's all these pointless "tween" artboards that the client or other viewers may have get lost in.
My suggestion is this: Add the ability to create a timeline for animations attached to a specific artboard or component. For instance, I create a component that is an a search icon. I want that to animate into a search bar when it is clicked. Rather than create a new artboard for each stage of animation, I'd like to be able to create a timeline, and add each step of animation to that component and define a trigger. Then, I can reuse this component throughout my design, utilizing the same trigger and animation throughout. This would reduce my overall file size and avoid creating endless numbers of artboards.
The other use case would be scroll animations or timed animations. These could be attached to specific artboards to control their interactivity at a greater detail with finer control.
I hope this makes sense but feel free to ask for clarification or examples, I would be happy to help however I can!
Morgan Caldbeck
supported this idea
·
-
1,197 votesfeature-under-review · 89 comments · Adobe XD: Feature Requests (Read-Only) » 02 : Prototype mode · Admin →Morgan Caldbeck
supported this idea
·
-
8,057 votes
Reopening the feature request, based on feedback.
Morgan Caldbeck
supported this idea
·
-
12 votesMorgan Caldbeck
supported this idea
·
-
3 votesMorgan Caldbeck
shared this idea
·
.png){kind=link}
.png){kind=link}
.png){kind=link}
.jpg){kind=link}
What you’re saying is correct, however I feel there are some improvements to be made for persistence. Let's say for example I'm creating a component with multiple states (default, hover and selected). If I make an instance of that component, and change the text on the default state to something different from the original, that text change does not persist to the other states. This is fine, because we can manually go to the different states and change each one. This gets monotonous though, especially when I have 20+ instances of a component that all have to have unique information. It means I have to go repeat this process of selecting the component, then the group and then the text inside, changing it 60+ times.
My suggestion is in the properties panel for the component, we add an "overrides" section. With this feature, I would be able to create the master component, then select the text I will be changing on future instances. I would then go to the "overrides" in the properties panel, click "+", and set that as a "string" (text) field. This way, when I create an instance, instead of clicking through the component and changing the text directly, I could instead type my new text in the "overrides" panel in the text field I created linked to that portion of text. The idea would be that this would update all the text for that layer across all states of that instance.
It would be nice to see this extend to other things as well such as background images, font styles, colors, etc. This would allow great flexibility and rapid data rich prototypes with the least amount of tinkering.