Cubelodyte

My feedback

  1. 10,761 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Cubelodyte supported this idea  · 
  2. 160 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Cubelodyte supported this idea  · 
  3. 993 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
    Cubelodyte commented  · 

    There are numerous requests for XD that could be translated to:

    Allow XD objects to behave as HTML objects with regard to CSS.

    In other words, one might expect that anything which could be done in CSS could also be done in XD.

    Example:
    A basic rectangle in HTML can have a border Top, Right, Bottom, or Left.
    XD provides no such ability.

    If we could apply CSS to XD objects directly in the interface, it would not only expand what we could design, it would also allow us to provide that CSS to our developers with no conversion or loss off integrity.

    Cubelodyte supported this idea  · 
    An error occurred while saving the comment
    Cubelodyte commented  · 

    Note to Adobe:
    I see this request has been "under review" for over 2 years. Here's a little something that might help you push it over the edge.

    Given that an enormous number of feature requests revolve around the ability to make styling adjustments to objects that mirror what's possible in CSS on a page, taking on this request would allow you to clear dozens of related requests in one stroke.

  4. 10 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
    Cubelodyte commented  · 

    @Adobe
    Please merge this with the other request (mentioned in my comment below https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/38972416-hover-triggers-to-all-elements-to-trigger-artboard).

    That story already has 64 votes. I'd hate for this to wait another year or 2 building up support when it's the request I intended to make almost 2 years ago when I first posted/commented on Hover triggers.

    An error occurred while saving the comment
    Cubelodyte commented  · 

    This is actually a duplicate of an existing request with a less appropriate name: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/38972416-hover-triggers-to-all-elements-to-trigger-artboard

    As of this writing, significant number of use cases for hover events still require navigation to another artboard.
    There will be an inevitable temptation on the part of Adobe to interpret this request as already handled by the States feature which when live in XD 24 (https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/12941394-tap-hover-effect).
    States are excellent for small changes like hover states on buttons (it would constitute a great waste of overhead to generate a duplicate artboard for every hover event on every button). So, kudos for the States feature.

    However, more complex transitions still require navigating to another artboard.

    Example: 3D Transformations (introduced in XD 34).

    Of course, when we say "Hover", we really mean "OnMouseOver". It is clear see now that the mistake we made in the original request was using the word "Hover" rather than "MouseOver". One can only imagine that the reason XD does not include "Hover" in the list of Triggers for Destination Transformations is because a hover event would be terminated the moment the calling artboard is exited or when the destination artboard is displayed. This would cause a looping between artboards; no fun!
    However, if the “OnMouseOver” event were a trigger that could navigate to another artboard, then a corresponding “OnMouseOut” event could be used to trigger a return to the first artboard.

    Win/Win!

    Another example of complex transitions that are not adequately handled with States:

    Another nice addition in XD 34 if the ability to have nested States. In other words, the ability for a component to enact a hover state while it is already rendering a hover State. This was achieved by officially supporting nested components.
    https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/38968075-hover-inside-hover-nested-hovers

    While this provides the literal behavior of hover within hover, it fails to produce a user experience that is comparable to what would occur on a web page.

    Example [see attached image]:
    - We create an icon that, when hovered, produces an overlay or dropdown.
    - Now we can hover over the new overlay and trigger a secondary hover event.
    - So far, so good.
    - However, the dropdown causes the parent component to render a larger rectangle which defines a scope that is equivalent to a <div> that encompasses the entire component. This larger rectangle includes a good bit of area not visibly covered by the original icon or the resulting overlay.
    - In a real-world implementatin (on a web page), the hover event would be terminated if the mouse cursor moves away from the original icon in any way other than to move over the newly generated overlay.
    - In XD, the cursor can now move over a non-existent [attached image] area above and to the right of the overlay without cancelling the hover event because that invisible area is considered part of the component.

    Note: I have had similar issues attempting to simulate an overlay dialog (documented in this request: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/41912431-honor-layers-z-order-in-prototype-interaction )
    The desired behavior would be to click anywhere outside the dialog to make it disappear. XD doesn’t appear to provide this ability. If a Tap Trigger is assigned to the larger layer beneath the overlay, the overlay layer fails to hide the proper portion of the background layer. The result is that by adding a Tap Trigger to the background, it is effective active across the entire overly; causing any Tap Triggers on the overlay layer itself to be swallowed up by the background Trigger.

    Cubelodyte supported this idea  · 
  5. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Cubelodyte shared this idea  · 
  6. 68 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
    Cubelodyte commented  · 

    It is clear see now that the mistake we made in the original request was using the word "Hover" rather than "MouseOver".

    Because of this, I have created a different request with a more accurate name:
    https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/42009670-add-mouseover-and-mouseout-to-list-of-triggers-for

    Note to Adobe:
    If you choose to merge this request with the one referenced above, please retain the newer name that describes this a MouseOver Mouseout rather than hover.
    I'm actually the author of both of these requests (not sure how I managed to log in with 2 names...probably due to a work account being added).

    Hopefully, between the 2 of these, we can get enough attention to the problem. My fear is that by keep this request alive with a name that references the "Hover" event, it will not receive the attention it deserves because of the impression that "Hover" events have been dealt with through the introduction of States.

    Cubelodyte supported this idea  · 
  7. 35 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    I honestly believe the functionality you requested here is currently available (several posts later in this thread suggest viable was to accomplish this).

    Sadly, this could have been handled in a much simpler way with the addition of 3D transformations introduced in the October release but Adobe opted to implement 3D effects outside the auspices of States.

    [See related request: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/41694019-allow-3d-transformations-in-states ]

    Cubelodyte supported this idea  · 
  8. 17 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    The following link shows an excellent example of why we need 3D Transformations to be State enabled: https://designwoop.com/css-3d-animation

    This feature is a great example of MVP. As thrilling as the 3D transforms are, they reside well within the "minimum" of Minimum Viable Product.

    I would be shocked to find that anyone who tried to use 3D transformations in this first iteration didn't attempt to make the transformation a State in 5 minutes or less.

    I'm a UX designer, so I fully recognize when a design/dev team anticipates extended use of a feature but the demands of any given release cycle dictate that it ‘go out without’ until a proven need is determined. This is an excellent practice in most circumstances. But when a use case is as obvious as this one, it's hard to justify putting out 3D transformations as a feature that is entirely divorced from the existing States functionality.

    Unfortunately, one would predict that the net result will be hundreds or thousands of Adobe XD users who will become very excited and then almost instantly very disappointed within a matter of.

    Note:
    This request is also mentioned in another request.

    https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/41825794-3d-transform-as-a-component-state

    Let's get these together to pool the votes.

    Cubelodyte supported this idea  · 
    An error occurred while saving the comment
    Cubelodyte commented  · 
  9. 3,204 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Cubelodyte supported this idea  · 
  10. 7,410 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Cubelodyte supported this idea  · 
  11. 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 » 02 : Prototype mode  ·  Flag idea as inappropriate…  ·  Admin →
    Cubelodyte shared this idea  · 
  12. 31 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    16 comments  ·  Adobe XD: Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Cubelodyte commented  · 

    Make the hints/tips stop!

    How many times to I have to have my work interrupted by a large hint dialog telling me how to use the features I've been using for 2+ years?!

    Cubelodyte supported this idea  · 
  13. 5 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 →
    An error occurred while saving the comment
    Cubelodyte commented  · 

    Kudo's to the creator of the Stacking/Padding functions.

    As an addon feature it would be immensely helpful for the Stacking feature to allow negative values for the intervals between stacked items.

    We have many designs that show up as overlapping objects.

    The ability to use negative values for spacing already exist for text grids.
    Can we get the same behavior for Stacking elements as well?

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

    We’ll send you updates on this idea

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

    Agree with all the comments so far.

    I had expected this to be a factor of the responsive resize and I'm very surprised that it is not.

    If the elements in a group are set to be fixed right or fixed bottom, one would expect that the stacking would follow this logic and expand left or up accordingly.

    Cubelodyte supported this idea  · 
  15. 197 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    27 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Cubelodyte supported this idea  · 
  16. 80 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    I'd really appreciate having a new group defaulted to "Rename" mode with the focus on the new Group.

    Once in this mode, hitting <Enter> or simply clicking away would leave it as "Group 1" (or whatever) without actually interrupting work flow. So, it would not impact working behavior in any negative way.

    However, it would save an enormous amount of time in naming groups if one could simply click <ctrl-g> after selecting multiple elements and then just start typing.
    The current alternative is that one must take one's hand off the keyboard, grab the mouse, find the group, and then successfully double click without opening the group instead of putting it into "Rename" mode.

    Cubelodyte supported this idea  · 
    An error occurred while saving the comment
    Cubelodyte commented  · 

    I love this.

    In addition, I'd also like to see a new group defaulted to "Rename" mode with the focus on the new Group.
    Once in this mode, hitting <Enter> or simply clicking away would leave it as "Group 1" (or whatever) without actually interrupting work flow. So, it would not impact working behavior in any negative way.

    However, it would save an enormous amount of time in naming groups if one could simple click <ctrl-g> after selecting multiple elements and then just start typing.
    The current alternative is that one must take one's hand off the keyboard, grab the mouse, find the group, and then successfully double click without opening the group instead of putting it into "Rename" mode.

  17. 2 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 →
    An error occurred while saving the comment
    Cubelodyte commented  · 

    Interesting idea, but I would certainly want it to be something a user could turn on or off in Preferences.
    Personally, I'd settle for having a new group default to "Rename" mode with the focus on the group name.
    Perhaps not everyone cares what the group name is, but I suspect most designers do more often than not.

    If the new group defaulted to "Rename" mode, hitting <Enter> or simply clicking away would leave it as "Group 1" (or whatever) without actually interrupting work flow. So, it would not impact working behavior in any negative way. However, it would save an enormous amount of time in naming groups if one could simple click <ctrl-g> and then start typing; the current alternative being that one has to take one's hand off the keyboard, grab the mouse, find the group, and then successfully double click without opening the group instead of putting it into "Rename" mode.

  18. 4 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 →
    Cubelodyte supported this idea  · 
  19. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Cubelodyte supported this idea  · 
    An error occurred while saving the comment
    Cubelodyte commented  · 

    This is a perfect example of a classic UX problem: "No matter how many times the user makes a mistake, they don't learn."

    This is a fundamental usability principle that points to bad usability design. If a user continues to use a feature or control incorrectly, it's the interface that's wrong.

    I'm not sure when this occurred, but there was definitely a time when you could rename an Artboard, Group, or page element and have the name stick when you click out (<Enter> key or not).
    Since that time, I continue to believe I've renamed an element only to look back later and see that it didn't take (because I failed to press <Enter>). After cursing XD, I fix the rename and might remember to hit <Enter> the next 2 or 3 times before I revert to the habit of typing a name and clicking away.

    One contributing factor to this behavior is the fact that Text elements not only don't require <Enter> to complete, it's not an option. <Enter> when typing in a Text element creates crlf. You must click away to accept what you've typed.

    To have 2 diametrically opposed behaviors for something that intuitively feels identical is maddening to the extreme.

  20. 45 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Adobe XD: Feature Requests » Other  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Cubelodyte commented  · 

    Agreed.
    There's a new update that allows the user to select previous links, but it only works if you've manually created multiple links on a document that has a continuous save history.

    It doesn't work if you:
    - Save a local XD document to the Cloud
    - Open a history version (focus of this request)

    In either of these cases, it's often essential to maintain the URL as links are published to various stakeholders.

    Possible Workaround for the author of this Request:
    Steps -
    1. Delete every artboard in current (official) version.
    2. Copy everything from the historical version
    3. Paste into current version
    4. Save

    Cubelodyte supported this idea  · 
← Previous 1

Feedback and Knowledge Base