Settings and activity
45 results found
-
432 votes
An error occurred while saving the comment 
Cubelodyte
supported this idea
·
-
306 votes
An error occurred while saving the comment Cubelodyte
commented
For the record, as with nearly every feature I have requested or voted on in this forum, you can already do this in Figma.
In Figma, if you have the Prototype tab selected, you can right-click anywhere, one of the options will be Remove All Connections.An error occurred while saving the comment Cubelodyte
commented
I just want to be able to publish a Developer doc after removing the interaction.
Once you've made an interaction, you can't publish all the artboards unless they are all wired. If you unwire them, you can't publish a Dev Doc anymore.It's getting very discouraging. Every (and I do mean every) time I do a search on "How to", I end up here in the feature request zone. Up until now, I've been reasonably impressed with how the product has continued to mature, but it hasn't taken me long to discover that XD is still not a viable design tool for professional work.
Cubelodyte
supported this idea
·
-
693 votes
Note: there’s a limited version of this feature already available. If you select an existing piece of text and then leave it selected while you use the Text tool to create new text, its style will match the piece of text you had selected.
An error occurred while saving the comment Cubelodyte
commented
For the record, as with nearly every feature I have requested or voted on in this forum, you can already do this in Figma.
An error occurred while saving the comment Cubelodyte
commented
Still under review?!
Not only will I never use the current default font family, we can't even change the font upon entry. We actually have to type the text first, then go back and modify it.Every time.
It get that there a several work-arounds. Basically, I duplicate text now because the tool is so frustrating.
How hard can it be to expose the default font in Properties somewhere?!
Cubelodyte
supported this idea
·
-
1,809 votes
An error occurred while saving the comment Cubelodyte
commented
In Figma, someone has created a plug-in for this.
Perhaps one exists in the XD community as well.Cubelodyte
supported this idea
·
-
78 votes
An error occurred while saving the comment Cubelodyte
commented
For the record, as with nearly every feature I have requested or voted on in this forum, you can already do this in Figma.
They handle History in a much more accessible and powerful way.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. SaveCubelodyte
supported this idea
·
-
81 votes
An error occurred while saving the comment Cubelodyte
commented
For the record, as with nearly every feature I have requested or voted on in this forum, you can already do this in Figma.
They don't use "stacked". Instead, they have frames with a powerful collection of Auto Layout constraints that allow the feature to grow in any direction.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
·
-
97 votes
An error occurred while saving the comment Cubelodyte
commented
For the record, as with nearly every feature I have requested or voted on in this forum, you can already do this in Figma.
They have a much more robust array of events including MouseEnter and MouseLeave.An error occurred while saving the comment Cubelodyte
commented
For the record, as with nearly every feature I have requested or voted on in this forum, you can already do this in Figma.
In fact, Figma has a much more robust array of events including MouseEnter, MouseLeave, etc.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
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-forNote 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.
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-hoversWhile 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
·
-
18 votes
An error occurred while saving the comment Cubelodyte
commented
For the record, as with nearly every feature I have requested or voted on in this forum, Figma does this.
Cubelodyte
supported this idea
·
-
1,540 votes
We announced CC Spaces in XD today at Adobe MAX! In a space, all members will be able to publish a link. More details to come!
An error occurred while saving the comment Cubelodyte
commented
For the record, as with nearly every feature I have requested or voted on in this forum, you can already do this in Figma.
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.
-
737 votes
An error occurred while saving the comment Cubelodyte
commented
Best workaround I've come up with:
Copy and paste component to new XD project file.
Make local.
Rename.
Copy and paste renamed component back to original XD project file.
Make local.
Edit new version to taste.UPDATE 11/30/2021
For the record, you can do this in Figma with <ctrl>+D.
It's just that simple.
Duplicate the main component and rename it.
Done.Cubelodyte
supported this idea
·
-
50 votes
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
·
-
2 votesCubelodyte
shared this idea
·
-
5 votesCubelodyte
supported this idea
·
-
73 votesCubelodyte
supported this idea
·
-
344 votesCubelodyte
supported this idea
·
-
3 votesCubelodyte
shared this idea
·
-
2 votesCubelodyte
shared this idea
·
-
116 votesCubelodyte
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.
UPDATE 11/30/2021
For the record, as with nearly every feature I have requested or voted on in this forum, you can already do some of this in Figma. While you can't necessarily detach the properties, you can get rid of them with a hotkey so that the entire artboard is visible. -
126 votesfeature-under-review · 21 comments · Adobe XD: Feature Requests (Read-Only) » 01 : Design mode · Admin →Cubelodyte
supported this idea
·
-
170 votesCubelodyte
supported this idea
·
For the record, as with nearly every feature I have requested or voted on in this forum, you can already do this in Figma.
File/Spec sharing is done completely differently in Figma. ReadOnly viewers are seeing the actual design document; not a secondary URL. This means that annotations can exist outside of artboard ("frames" in Figma).
It also means that users can comment directly in the project file rather than in a secondary URL. This keeps the communication to a central location.