"Scaling Tool" (scale stroke weight, shadow effects & corners when resizing)
Ability to scale attributes proportionately. When creating shapes, buttons, or icons within XD sometimes they need to be scaled to different sizes. Currently when scaling these shapes, buttons, or icons created within XD we can no scale some of the attributes proportionately.
As an example I create a container box with a stroke, border-radius, shadow, and paragraph text. If I need to scale proportionately, like say 50%, the stroke, border-radius, shadow, and paragraph text don't scale proportionately.
(Currently using Windows Beta Version: 0.6.8.6)
Courtney @ Global Work & Travel commented
Why doesnt XD have the most basic, fundamental ability to scale a stroke? when i scale a graphic with a stroke i should have the options to scale stroke and effects uniformly just as illustrator has. it isnt rocket science, this is basic, basic stuff. please add it
Yes please, we need this
Ron Driessen commented
just checked in to see if this is fixed yet,.. but no.... Really need this
Noble Woods commented
Was working on some designs in XD and I had to ditch it for Illustrator because this basic option doesn't exist in XD
As somewhat a newbie to XD, (not to design tools) I just made an assumption that something as simple as scaling my SVG's was a BASIC feature. Alas, I searched the help and tried different things to proportionally scale my SVG - but as you and Adobe know, its a mess!.
Coming here proves that this simple feature is not available. How on earth with all of the updates you have had to this product has this gone un-fixed.
Worse still is that this request to fix it goes back to March 2016 !! - So not only are you failing to fix basic features for a design tool you are failing to listen to your customers.
Lack of this basic feature is what is known as a Fuster Cluck !
C'mon team Adobe - Pull your finger out.
Another example of a software made by Adobe that should have all functionalities that they have integrated in their other design programs. Specially Illustator that seems to be close to XD as managing vectors. You would imagine that the team of XD and the team of Illustrator are integrated as it should be as the user is really working with both programs at the same time.
Rick Bond commented
Thank you for this. I suggest that the Adobe Xd dev team look at Adobe Illustrator > Scale Strokes and Effects preference as it does exactly what the OP and I need *I think*
Rather than change the scaling operation itself, an XD function to Make Vector (like outline stroke in AI) within XD would probably be appropriate. I already have to fumble around responsive resize all the time and don't need another scaling option.
Are there any workarounds other than using AI?
Copy elements, paste in illustrator, select all, object>path>outline stroke, select all and copy, paste back into XD.
Stroke will now scale proportionately with other elements
Would love borders that scale with size. If I have a 100x100 rectangle with a 10px border I'd like the option to scale the border with the rectangle (1000x1000 rectangle = 100x100 border).
Adobe XD keeps disappointing me
Crazy that this isn't fixed yet.
Pierre Khoury commented
So obvious to have, but still not there.
A quick workaround for it is, keep illustrator open, import your svg to illustrator, scale to desired size, copy to adobe xd 2020.
Unnecessary effort, but beats the manual labor in xd.
Hope this helps.
Paul Bredenberg commented
Yes, please add this. I use SVGs in layouts for UI design and it is tedious to have to manually adjust strokes every time I import an SVG.
Please do this
As if this isn't a feature already...
Marco Duarte commented
It really is something that upsets me a lot, it is not possible that with all the updates we have this is not resolved.
Max Laschon commented
How is this not fixed yet?
It's a 2016 issue.
It's really hard to work with SVGs images from almost any source. (ionicons for example). Every SVG imported is huge and on scaling down I lose all the Icon appearance. It's soo annoying and feels so wrong that this should be treated as a bug and not a new feature