Jump to content
footof

Designer: Expand stroke is completely broken

Recommended Posts

Right… I guess it's not just me. Hoping this does get sorted soon though… This is super important for me because I create icons at 16x16 so when expanding a stroke distorts the shapes, it's a big deal.

The main reason I am using using AD is because Sketch's vector tool is busted and I can't rely on it for complex icon work. So if I also can't rely on the accuracy of AD as a vector tool, there's not much benefit in me using it in the first place.

For clarity, I'm not after feature-parity with Illustrator either. But I do expect the features it does have to work as expected (especially something as fundamental as expanding/outlining a stroke).

Share this post


Link to post
Share on other sites

Same here. I´ve purchased v 1.7 and that awful bug still there :( Come on you Affinity Team! This is not a minor issue. We, the buyers, are designers. It´s very important that the expand stroke function works properly. I really love Affinity Designer, but I still have to stick to AI due to that bug. 

Share this post


Link to post
Share on other sites
On 10. Juli 2019 at 9:03 PM, PaolaB said:

It´s very important that the expand stroke function works properly.

For all who don’t want to use other apps (as workaround): 

First increase the scale of the objects, expand them, then scale them down again to their original size. Use a maximum factor of about 1000.

 

You can get great results by using another problem as a “solution”: Increase “DPI” in “Document Setup…” (best before you start your work). For example use 21893 dpi if the page size is not bigger than (DIN) A4.

Share this post


Link to post
Share on other sites
22 hours ago, Oval said:

For all who don’t want to use other apps (as workaround): 

First increase the scale of the objects, expand them, then scale them down again to their original size. Use a maximum factor of about 1000.

 

As mentioned before, this only makes it similar visually. The node count and placement is still broken so that makes it unusable for further node modification. That is only a workaround if you only need vector for scalability, not further editing.


Mădălin Vlad
Graphic Designer

Share this post


Link to post
Share on other sites

I'm also suffering from this bug (Desktop version on Windows 10). Please move this up on your prio list, as expanding strokes is a super common thing to do.

Share this post


Link to post
Share on other sites

I can't believe this bug hasn't been fixed since 2017... Come on guys this is basic feature for an illustration tool! I've been a long time user of Affinity Designer but I'm getting more and more frustrated (it's like the "select same color tool" that has been asked 4 years ago). So much that I've stopped recommending AD, without this bug patched it's just a broken illustration tool.

I hope you will change my mind and bring a fix asap.

Share this post


Link to post
Share on other sites

Hi Etienne,
I'm sorry for the inconvenience this issue have been causing you. The teams have been busy with the changes required for Publisher interoperability and with Publisher's release itself. With it now released we are looking into some of these longstanding issues. Thanks for your understanding.

Share this post


Link to post
Share on other sites

my understanding for this problem is zero!

this bug is sooo old and it is impossible to make icons for websites - which i would like to do very often. i have to look for another program now, which can be used for making icons. it's a joke that this is not being fixed. it worked in the beginning of affinity designer, so this can't be a very big problem to fix.

affinity started very well and hopeful, but because of all the different versions coming out they lost focus on the most important thing: reliability and fast bug fixing. very sad...

 

Share this post


Link to post
Share on other sites
On 19. August 2019 at 12:49 PM, bandit69 said:

i have to look for another program now

Well, perhaps the next months we’ll get a fix (because finally someone should have time after the work of the iOS thingies … contradicts a bit the information of MEB).

In the meantime: You can get great results by using another problem as a “solution”: Increase “DPI” in “Document Setup…” (best before you start your work). For example use 21893 dpi if the page size is not bigger than (DIN) A4.

Share this post


Link to post
Share on other sites
On 8/12/2019 at 6:09 AM, MEB said:

The teams have been busy with the changes required for Publisher interoperability and with Publisher's release itself. With it now released we are looking into some of these longstanding issues. Thanks for your understanding.

I would like to suggest in the future that prioritizing new programs and projects over critical functionality of existing products is a very poor choice. It makes it seem that the company wants new customers and more money over loyal satisfied professional.  

I don't think that Serif feels that way at all, so please don't act that way in the future. I know you folks have taken a sad beating in this thread over the years, it's very flustering I'm sure on that end of things too.   Please understand that for many of us, this function is so at the core of our work flow that it was (and is) hard to understand how anything else was ever getting worked on while it was still broken.   Please assign the correct folks to this right away if it has not already happened. Let us know that it is not on "the list" but actually on the "workbench". Please focus on being the responsive agile company that drew us all in in the first place.

Share this post


Link to post
Share on other sites
12 hours ago, Rivka said:

I would like to suggest in the future that prioritizing new programs and projects over critical functionality of existing products is a very poor choice. It makes it seem that the company wants new customers and more money over loyal satisfied professional.  

I don't think that Serif feels that way at all, so please don't act that way in the future. I know you folks have taken a sad beating in this thread over the years, it's very flustering I'm sure on that end of things too.   Please understand that for many of us, this function is so at the core of our work flow that it was (and is) hard to understand how anything else was ever getting worked on while it was still broken.   Please assign the correct folks to this right away if it has not already happened. Let us know that it is not on "the list" but actually on the "workbench". Please focus on being the responsive agile company that drew us all in in the first place.

+5000 on this. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×