Settings and activity
10 results found
-
4 votes
An error occurred while saving the comment Julie Jacob supported this idea · -
76 votes
An error occurred while saving the comment Julie Jacob commentedFURTHER, I have a button component, that component is part of a button group component that, in turn, is part of a control modal component. I need to be able to attach one of two actions to the button click/tap. Either one that changes the state of the button group, or one that changes the state of the modal (grandparent) component. We just need to have more capabilities between these nested components, period. And we needed this last year.
Julie Jacob supported this idea · -
956 votes
An error occurred while saving the comment Julie Jacob commentedThis is vital. States are useful only if they have the ability to interact with and impact the surrounding and vice versa. Please implement this!
Julie Jacob supported this idea · -
125 votesJulie Jacob supported this idea ·
-
157 votesJulie Jacob supported this idea ·
-
184 votes
An error occurred while saving the comment Julie Jacob commentedI'm working on a prototype and need to be able to demonstrate the difference in behavior on a touch screen between a single tap or a double tap. Tap and hold would also be really helpful. Please add more interaction features!
Julie Jacob supported this idea · -
1,809 votes
An error occurred while saving the comment Julie Jacob commentedSIX YEARS later, 1534 votes and still no feature... disappointing.
Julie Jacob supported this idea · -
737 votes
An error occurred while saving the comment Julie Jacob commentedThis is huge. I have a navigational component that I need to use on many pages across multiple prototypes. The navigational component has a variety of states which have varying navigational options. In each prototype, those navigational elements link to various boards unique to that prototype. But without being able to have a local "Main" instance of that navigational component, I can't assign links to those navigational options across the prototype, unless I can plan it out before propagating the component. But even then, if there is a change, I have to go and edit the linkage for EVER SINGLE INSTANCE.
Julie Jacob supported this idea · -
223 votes
An error occurred while saving the comment Julie Jacob commentedCan't tell if these requests actually amount to action, since this has been something requested for years, but I'm putting my voice behind it. We NEED this feature!
Julie Jacob supported this idea · -
3,888 votesfeature-in-the-backlog · 526 comments · Adobe XD: Feature Requests (Read-Only) » 01 : Design mode · Admin →Julie Jacob supported this idea ·
An error occurred while saving the comment Julie Jacob commentedThis seems like a massive oversight. Lists are so commonly used. Please implement this soon!
I am also having this same issue. It seems components are VERY limited when dealing with a variety of prototyping scenarios. I feel that this is overdue for some attention.