Morgan Caldbeck

My feedback

  1. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Morgan Caldbeck commented  · 

    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.

    Morgan Caldbeck shared this idea  · 
  2. 6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Morgan Caldbeck supported this idea  · 
  3. 643 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    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!

  4. 357 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    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.

  5. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Morgan Caldbeck shared this idea  · 
  6. 984 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Morgan Caldbeck supported this idea  · 
  7. 1,069 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Morgan Caldbeck supported this idea  · 
  8. 1,424 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Morgan Caldbeck supported this idea  · 
  9. 2,022 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Morgan Caldbeck supported this idea  · 
  10. 6,280 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Morgan Caldbeck supported this idea  · 
  11. 4,839 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Morgan Caldbeck supported this idea  · 
  12. 237 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Morgan Caldbeck supported this idea  · 
  13. 110 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Morgan Caldbeck supported this idea  · 
  14. 159 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    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  · 
  15. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Morgan Caldbeck shared this idea  · 
  16. 2,060 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    67 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Morgan Caldbeck supported this idea  · 
  17. 2,925 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Morgan Caldbeck supported this idea  · 
  18. 358 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    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  · 
  19. 631 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Morgan Caldbeck supported this idea  · 
  20. 64 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    15 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Morgan Caldbeck commented  · 

    I would love to see flexbox-like auto distribution in xd. When designing websites, I often feel as though it’s a little clunky responsively, and I have to move to designing the mobile version separately from the desktop/tablet experience. This can create a disconnect for the client and the developer.

    What would be beneficial would be to set rules for components and groups, say multiple items in a box. Being able to specify options such as “space between”, “space evenly” and “space around” would allow greater flexibility when designing responsive applications. It would also allow us to nest items more easily and really speed up the design process.

    I would also like to see the ability to set a margin or padding on the containers to help with creating consistent design without having to manually drag until smart guide recognizes placement. Setting margin and padding would help keep things organized during a resize event.

    Also, the option to define stacking of elements or components at different widths would be extremely useful, though could be accomplished through other means.

    All in all, I think these features would help web designers to create more consistent experiences, and push them to think from a responsive mindset. Inclusive design is always more effective than trying re-invent your experience after already having defined a beautiful idea in a specific screen size, and it will make developers much happier. 😁

    Morgan Caldbeck supported this idea  · 
← Previous 1

Feedback and Knowledge Base