Pete Conway
My feedback
-
1 votePete Conway
commented
I just had the same issue occur again and managed to get a screenshot of the error. It would be helpful if this could be addressed soon as I don't want to lose more work, and it is currently preventing me from doing what I would ideally like to be able to do with components
Pete Conway
shared this idea
·
-
12 votesPete Conway
supported this idea
·
-
40 votesPete Conway
supported this idea
·
-
60 votes
Hi All -
We’re working on a fix for shadows not to be included within the component bounding box.
I’ll keep you posted once the fix is out.
Thanks,
SherifPete Conway
supported this idea
·
-
972 votes
We’re working on a visual versioning system for XD documents. You could see a preview here: https://youtu.be/pf35qphKOWE?t=1h7m51s
Pete Conway
supported this idea
·
-
1,099 votesfeature-started · 48 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
Add multiple states inside symbols / smart objects
-
Capture.PNG 76 KB -
Screen Shot 2018-12-16 at 15.39.59.png 118 KB -
Screen Shot 2018-12-11 at 1.53.14 PM.png 396 KB -
Group 625.png 21 KB -
toggle1b.gif 66 KB -
Screen Shot 2018-10-24 at 12.14.57.png 11 KB -
Screen Shot 2018 08 30 at 5 40 04 PM.png 225 KB -
Screen Shot 2018-07-17 at 12.25.55.png 21 KB -
Kodi_Example.mp4 5374 KB -
Single_-__Editing_states_of_single_control.png 538 KB -
Editing_states_of_single_control.png 1157 KB -
Editing_states_of_single_control_-_1.png 1160 KB -
Editing_States_of_controls.png 1157 KB -
Editing_States_of_controls_–_1.png 1157 KB -
Artboard_-_States_of_controls.png 632 KB -
Component_(nested_states_as_stacked_artboards.mp4 21440 KB -
states.PNG 43 KB -
navigation.PNG 194 KB -
Interaction.png 48 KB -
Shapes-and-property.png 72 KB -
Initial.png 62 KB -
Screen_Shot_2017-03-13_at_11.28.43.png 90 KB -
Screen_Shot_2017-03-13_at_11.27.41.png 28 KB -
Edit_smart-object.jpg 136 KB -
Design_mode_while_smart-object_selected.jpg 129 KB
1,154 votesfeature-in-the-backlog · 115 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
-
1,742 votes
We think you’re going to really, really dig the plugin integrations we’re making available later this year :)
Hoyle
Pete Conway
supported this idea
·
-
3 votesPete Conway
shared this idea
·
-
395 votesfeature-under-review · 26 comments · Adobe XD: Feature Requests » 03 : Sharing on the web · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
1,051 votesfeature-started · 23 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
7,131 votesfeature-started · 839 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
281 votesPete Conway
supported this idea
·
-
736 votesfeature-under-review · 59 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
1,412 votes132 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →
Hi, everyone! In the August release of Adobe XD, we’ve introduced the ability to consume colors and character styles from your existing Creative Cloud library. We’re working on bringing you the ability to bring in graphics (both bitmaps and vectors) as well, so we’re keeping this feature open until we get that out the door.
In the meantime, if you have feedback on what we’ve already released, please do file a new idea so that we can get community feedback on it.
If you haven’t seen the update yet, launch the Creative Cloud desktop application, click on the gear icon, and select “Check for App Updates.”
-Elaine
Pete Conway
supported this idea
·
-
408 votes
As we shared at MAX this year, we’re planning on collaborative workflows for the future. Please check out this recording of our presentation, starting at about minute 27:15 for a vision of how we’re going to handle collaboration: https://www.youtube.com/watch?v=dn_9u1qtQ8s&t=1412s
We’d love your feedback on the concept!
-Elaine
Pete Conway
supported this idea
·
-
4,855 votesfeature-started · 633 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Pete Conway
commented
I'm sure someone has already mentioned this but it would be useful if these could be triggered in different ways, e.g. trigger on click, trigger on page page open etc.
Pete Conway
supported this idea
·
-
497 votesfeature-started · 100 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
19 votesPete Conway
supported this idea
·
-
353 votesfeature-in-the-backlog · 16 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Pete Conway
commented
When testing prototypes with end users we have a limitation in that we can't allow them to input text and it breaks the illusion when they have to, for example, tap a search box which will immediately populate or hyperlink to another screen. It would be great to be able to allow them to enter values (e.g. string, date, check box, radio group, toggle). This is particularly important when doing A-B testing between a working website and a prototype - it breaks up the user flow and forces the observer to step in to explain. It can also affect the interaction of the user as it can become confusing and unexpected, and it may colour their feedback if they can clearly tell which is the prototype and which is the original. In Proto.io it is possible to enter data which makes it very compelling and it is currently appealing as an alternative to Xd.
Another user has proposed a similar feature where alternative actions occur based upon data entered - whilst this would be nice it seems pretty complex and perhaps more than is necessary in the first instance. Perhaps a simpler model would be to allow a component to inherit the data value of another component, so that data entered on the first artboard is replicated on the second - these components would effectively be tied in terms of data but would be represented very differently visually.
Maybe an approach for this could be:
Phase 1 - add a component library which allows for data entry
Phase 2 - allow for captured data to be tied to a elements across other artboards (e.g. I login with a user name and this can then be displayed on a subsequent screen, or a search string can be left in the search box on a subsequent artboard).
Phase 3 - allow for conditional links between artboards based on selectionsPete Conway
supported this idea
·
.png){kind=link}
I forgot to mention that the document was already one that had been saved at a previous point and it was saved on my computer, not as a cloud file.