Settings and activity
27 results found
-
279 votesIsadora supported this idea ·
-
81 votesIsadora supported this idea ·
-
313 votes
Please note that stacks is a feature that is intended to be used at design time, and does not dynamically shift the stack in preview. I’m going to rewrite this particular request to be more precisely about the latter suggestion.
Isadora supported this idea · -
164 votesIsadora supported this idea ·
-
6 votes
An error occurred while saving the comment Isadora supported this idea · -
16 votes
Got it! Adjusted the title to reflect your clarification.
An error occurred while saving the comment Isadora commentedI got a new computer and display. Of course with the better resolution everything is tiny. Now the XD interface is completely unreadable. I keep leaning in and squinting while I work, which is not sustainable. Please Adobe make the XD interface more accessible.
-
1,809 votesIsadora supported this idea ·
-
192 votes
-
516 votes
-
27 votesIsadora supported this idea ·
-
709 votesIsadora supported this idea ·
-
956 votesIsadora supported this idea ·
-
704 votesIsadora supported this idea ·
-
1,009 votesIsadora supported this idea ·
-
56 votes
An error occurred while saving the comment Isadora commented"Go to next artboard" and "Artboard Quick Navigate" are good substitutes while we wait for a feature like this
Isadora supported this idea · -
254 votesIsadora supported this idea ·
-
1,526 votes
An error occurred while saving the comment Isadora commentedI would like multiple canvases within one file so I can have different userflows within the same file, but not have them all visible at the same time.
Isadora supported this idea · -
1,851 votesIsadora supported this idea ·
-
3,888 votesfeature-in-the-backlog · 525 comments · Adobe XD: Feature Requests (Read-Only) » 01 : Design mode · Admin →Isadora supported this idea ·
-
2,901 votes
We are planning for more robust text support for RTL fonts in the future.
-Elaine
Isadora supported this idea ·
These default settings make it look like there's something wrong with your prototype because they don't reflect the vast majority of how hovers work in the real world. During user testing, participants are confused because they have to wait .3 seconds until they can click on a button with a hover state (which is pretty much all of them). It's also frustrating when you're trying to put together a presentation of your prototype and navigate through it quickly. All of these .3 seconds add up. The work around, as the original post says, is to reset each hover interaction, but I rarely have time to do that.