Cubelodyte

My feedback

  1. 4,586 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Cubelodyte supported this idea  · 
  2. 41 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Over the course of a complicated design project, many component assets can be added to a project document and then subsequently removed for various reasons.
    In order to keep the document assets pool clean and manageable the designer will want to delete assets that have no instances in the document.

    This could be achieved by any of 3 methods.

    1. Filter document assets to only show components with "No instances". Then the designer could select them all and "delete".

    2. Sort document assets by number of instances in document. This would group the components with no instances at top or bottom allowing the same bulk delete ability.

    3. Provide a single command to "Delete all unused components".

    These function could, of course, apply to colors and font assets as well.

    Cubelodyte supported this idea  · 
  3. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    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 →
    Cubelodyte shared this idea  · 
  4. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    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 →
    Cubelodyte supported this idea  · 
  5. 133 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    31 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Cubelodyte supported this idea  · 
  6. 1,175 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Cubelodyte supported this idea  · 
  7. 60 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Cubelodyte supported this idea  · 
  8. 310 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    52 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Cubelodyte supported this idea  · 
  9. 1,179 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Cubelodyte commented  · 

    So, shall we assume that 4 years and over a thousand upvotes isn't enough to make this any sort of priority?
    Can we get this out of backlog and into production?

    You've done so much work towards collaboration and then shut the door on it before ever making it truly viable. Collaboration is essentially impossible without the ability for anyone working on a document to also be able to publish it.

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

    4 years and still in the backlog.
    I would dearly love to have more insight into how things get prioritized. We have only a team of 2 and this issue represents a major blocker for collaborative design. I can only imagine how difficult this must make the work of larger teams.

    Perhaps if we address this as a security issue, it will get more traction.

    Given that the only viable workaround here is for teams to share a login, Adobe might want to consider the ramifications of sharing login information.

  10. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    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 →
    Cubelodyte shared this idea  · 
  11. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    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 →
    Cubelodyte shared this idea  · 
  12. 105 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    31 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  · 

    Switching between layers and assets is very cumbersome (even with shortcut keys -- ctrl+shift+y is really requires 2 hands) and often, it becomes necessary to see which layer object has focus while either applying colors or adding.

    Another need is to be able to see the full pasteboard without the intrusion of the assets/layers panel or the properties. Not all design is for mobile. When designing a screen for a computer interface, it would be greatly helpful to be able to use the entire screen during the creation process.

    Many of us use multiple screens so the ability to move these adjustment panels/windows onto a separate viewing surface while working with a full screen to view the active artboard(s) would greatly enhance our workflow.

    By making these windows (Layers and Assets) dockable (and, more importantly, undocable) the user can increase visibility on the pasteboard as well as working with both assets and layers simultaneously.

  13. 15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Cubelodyte supported this idea  · 
  14. 108 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Cubelodyte supported this idea  · 
  15. 11,448 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Cubelodyte supported this idea  · 
  16. 162 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Cubelodyte supported this idea  · 
  17. 1,041 votes

    We're glad you're here

    Please sign in to leave feedback

    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.

  18. 18 votes

    We're glad you're here

    Please sign in to leave feedback

    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  · 
  19. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Cubelodyte shared this idea  · 
  20. 73 votes

    We're glad you're here

    Please sign in to leave feedback

    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  · 
← Previous 1 3

Feedback and Knowledge Base