Settings and activity
24 results found
-
1 vote
Andrew Hart
shared this idea
·
-
6 votesAndrew Hart
shared this idea
·
-
737 votes
An error occurred while saving the comment Andrew Hart
supported this idea
·
-
6 votesAndrew Hart
shared this idea
·
-
109 votes
An error occurred while saving the comment Andrew Hart
commented
Agree that this is needed for both objects and artboards, and should have a shortcut as well as being available from the right button menu.
For artboards, I would prefer it if adobe xd did try to align the pasted artboard with the surrounding artboards where possible.
Specifically:
If the space surrounding the mouse is not large enough for the pasted artboard, then paste at the location of the mouse.
If the space surrounding the mouse is large enough for the pasted artboard, then attempt to align it within that space to the surrounding artboards.
Otherwise, paste into the available space as best as it will fit.
For objects within artboards I would also prefer if it also tried to do some minor alignment in certain circumstances.
Specifically:
If the object is being copied and pasted within the same artboard, and the mouse position is clearly above or below the original copied object, then the pasted object should be horizontally aligned with the original.
Similarly, if the object is being copied and pasted within the same artboard, and the mouse position is clearly to the left or right of the original copied object, then the pasted object should be vertically aligned with the original.
Otherwise the object should be pasted at the current mouse position
Andrew Hart
supported this idea
·
-
5 votes
An error occurred while saving the comment Andrew Hart
commented
When moving an artboard or object within an artboard using drag and drop with the mouse matching gaps are highlighted with a pink bar.
However when moving an artboard or object using the mouse keys matching gaps are not displayed.
I cant think of a reason why this should be the case, and I would love it if the two methods of moving behaved more consistently.
Andrew Hart
supported this idea
·
-
2 votesAndrew Hart
shared this idea
·
-
1,774 votesfeature-under-review · 81 comments · Adobe XD: Feature Requests (Read-Only) » 01 : Design mode · Admin →Andrew Hart
supported this idea
·
-
7 votes
An error occurred while saving the comment Andrew Hart
commented
I have quite enjoyed exploring all the possibilities using states and prototype triggers, but it seems bizarre to me that I have to experiment and build my own components to achieve functionality such as ... for example
a. Implementing radio buttons where only 1 can be selected
b. Dropdown fields
c. Implementing enabling of a button when a form field is filledI imagine that beginners would find it useful to have even simple to implement pre-packaged components such as form field containing an in field prompt that disappears when you click on the field and a hover over action available
Andrew Hart
supported this idea
·
-
9 votes
An error occurred while saving the comment Andrew Hart
commented
I often use the layers panel to copy and paste elements. E.g. if I want to copy an element of a main component to another component.
Currently, when I paste into the new component the elements are pasted some distance from the target component. I cant imagine a situation where the current xd chosen paste location is anywhere near where the user would want it to be located.
Andrew Hart
supported this idea
·
-
29 votesAndrew Hart
supported this idea
·
-
76 votes
An error occurred while saving the comment Andrew Hart
commented
SOLUTION FYI, if I understand you correctly, you can actually achieve this by adding a dummy enclosing group for each of the components that you wish to nest. You can then use these groups to create a component add triggers onto each group to change the state of the enclosing component. You need to remove the triggers from the sub-components or you get unpredictable trigger results. However, you do end up with a subcomponent that will modify its attributes when the main component is edited.
E.g. You have a traditional radio button component with 2 states. Unselected/Selected
You want a block of radio buttons where only one of the radio buttons can be sekected at any one time.
I.e. If you click on any of the radio buttons the other radio buttons are de-selected.I'm sure that's enough info, but I like to be thorough, so below is a step by step
Add one radio button component to your artboard
Remove all state change triggers in this component
Copy the modified radio button component as many times as required
Right click on each radio button component and select Group.
Select all the radio button groups and create a component
Create a new state in the enclosing component, one for each radio button
E.g. Radio button 1 selected; Radio button 2 selected etc
For each state drill down in the appropriate radio button to the embedded component to change its state to selected
For each state, add a Tap trigger on each radio button group (ie not the encloded component) that chooses the appropriate state of the enclosing component.Job done
FOR ADOBE XD
Even though it is possible to achieve the desired result using this procedure, I suspect that many people willnot easily figure this out. You should be able to do this without going through the rigmarole of enclosing each component in a dummy group. I consider this a bug.
Andrew Hart
supported this idea
·
-
3 votes
An error occurred while saving the comment Andrew Hart
commented
Currently, when I return to a previous artboard the component states on that artboard are returned to their default state.
I would like to be able to specify that the states of components on the artboard persist.
For this to be truly useful, we would need to be able to limit the scope of the persistence. I.e. We would need to group several artboards together as a persistence group. If the user stays within this group, the persistence remains, but as soon as the user exits the group to another artboard, if they return to an artboard within that group the component states are once again set as default.
An example of what this would allow is:
Form filling across several artboards and allowing the user to go backwards (previous artboard) and see changes that they previously made such as Toggle, checkboxes etc that were implimented using component states.
Andrew Hart
supported this idea
·
-
279 votesAndrew Hart
supported this idea
·
-
428 votes
I’m going to leave this one open, but please note that you can do this already using auto-animate and the time trigger.
An error occurred while saving the comment Andrew Hart
commented
I have put in a request to add the ability to set a Time trigger for a component state change. Since component state change already supports auto animate this accommodate this request.
I have also seen another request to allow components to change the state of other components on the artboard. This could also be achieved by extending the component trigger mechanism, not just with a Time trigger, but also with a 'other component state change' trigger.
-
10 votesAndrew Hart
supported this idea
·
-
306 votesAndrew Hart
supported this idea
·
-
956 votes
An error occurred while saving the comment Andrew Hart
commented
I suggest this is done by adding the ability to Trigger a component state change when another component on the artboard changes state.
I have already made a request to allow a component to change state based on a Time event, so both requests could be grouped into a general upgrade to the component state change trigger mechanism.
Andrew Hart
supported this idea
·
-
1,472 votesfeature-under-review · 342 comments · Adobe XD: Feature Requests (Read-Only) » 01 : Design mode · Admin →Andrew Hart
supported this idea
·
-
834 votesAndrew Hart
supported this idea
·
I presume you will implement this with a right click option in the component panel. However if you choose to also implement this as a right click option of a component on the artboard, which adds the duplicate component to the artboard (A feature that I would like), I would request that the duplicated component be tagged as a main component, not just an instance.