zstekovic

Hi everyone... I'm starting to use Affinity products more and more, and they are polished to the degree. But Studio part (right side) easily is turning into mess as you work on the project.
Adobe solve this with small docking icons that work really well (attached).
Maybe Affinity should do the same. It's just handled really well on Adobe side.
Some solution like this should be implemented. 

Hi everyone... I'm starting to use Affinity products more and more, and they are polished to the degree. But Studio part (right side) easily is turning into mess as you work on the project.
Adobe solve this with small docking icons that work really well (attached).
Maybe Affinity should do the same. It's just handled really well on Adobe side.
Some solution like this should be implemented. 

Yes, that would be good method for simple files, but try it on fonts, or better outlines around the fonts, contours. Also program to program workarounds are not recommended in any kind of workflow.

It just works.

Not at all!
I'd be just fine with the reliability of CS5(.5) because that's what I'm still working with.
As noted, save for a few relatively unimportant spots where Illustrator CS5 wil predictibly crash on Mac OS El Capitan (which is what I'm mainly working with, for too many reasons that I won't go into here), it still does exactly what I need it to do. Same for Photoshop and InDesign CS5.5. Some of their tools are still very "20th century", but having been working in the digital domain for more than 25 years, I can deal with that.
Heck, I made layouts with AI CS5 that look like this:

The file is 66 MB without PDF compatibility (would be a few hundred MB with PDF embedded) and it takes a few minutes to load. It contains a full size vinyl LP gatefold sleeve layout, the corresponding CD Digipak layout with a 16-page booklet, and the record and disc labels layouts.
All text is still "live", and all of it has my favorite Illustrator "killer feature" applied, the Roughen vector effect. Plus many other effects, filters, transparencies, you name it, where needed.
Here's a detailed view:

It went to print simply by exporting each page to PDF/X-3 using the built-in PDF exporter. The flattened PDF/X-3 of the LP sleeve is 100 MB. It printed without hicks.
The resulting product is here: http://munster-records.com/en/label/vampisoul/product/czech-up-vol-i-chain-of-fools Everything was printed exactly as intended.
Frankly, for the next release I have split each packaging part into separate files because the file load and redraw times were a tad a too long indeed…
When Designer (or any other competitor) is ready to accomplish such a project as well, then I'll be ready for a full switch.
And yeah, the Roughen effect is a must!
I'm definitely not going to join the CC rip-off.
I'm a professional graphic designer, self-employed since 1988.
Then it's ultimately not worth for me to even look at that.
***
Alright, we're getting very off topic…

No, you used “perfect fit”. We just like to have (at least) the same accuracy like in Inkscape:
 

 
10 points are not enough for that curve.

Yes, I know that they will announce when it's fixed, but for vector program this is unacceptable. I'm using CorelDraw to do my work (with Adobe CS6, SAi Flexi, and other specialized programs for rip/print/cut/engrave stuff), so I do not use Designer for serious work, but I bought it, and support it in my place of business. But this bug is now running joke. Vector program that is not precise is not good program, especially if your work depend on it. Even free programs that come with cutters nail this down (Graphtec, Roland, Gerber Omega...).
I hoped they did mitigate the problem with all other improvements they did (program is 400MB bigger in size then 1.6.1 version).
Also, you would think that you can bypass problem with this method, but I'm doing machine cutting, and regardless that you see clean line in Designer, it's broken at export (for other programs that follow standards it's unusable).
Look kind of OK, but it's not OK, not at all OK.

Just to report that Expand Stroke function still suck.
Check attached file, and zoom in first on top one, then on bottom.
 
CPP TEST.afdesign

Yes, I know that they will announce when it's fixed, but for vector program this is unacceptable. I'm using CorelDraw to do my work (with Adobe CS6, SAi Flexi, and other specialized programs for rip/print/cut/engrave stuff), so I do not use Designer for serious work, but I bought it, and support it in my place of business. But this bug is now running joke. Vector program that is not precise is not good program, especially if your work depend on it. Even free programs that come with cutters nail this down (Graphtec, Roland, Gerber Omega...).
I hoped they did mitigate the problem with all other improvements they did (program is 400MB bigger in size then 1.6.1 version).
Also, you would think that you can bypass problem with this method, but I'm doing machine cutting, and regardless that you see clean line in Designer, it's broken at export (for other programs that follow standards it's unusable).
Look kind of OK, but it's not OK, not at all OK.

I haven't noticed a single insult here, you seem to be a bit oversensitive, don't you think?
Well, I'm a frustrated user who paid for "professional and most precise vector drawing tool" and that is clearly not true (now for years).
Please, stop with euphemisms, Expand Stroke's current state isn't unfortunate. It's catastrophic. And it's not just current state, it's been like that for years and sadly, it wasn't Serif's priority to fix this. Instead, we got arrowheads and isometric drawing. How often will people use those compared to expand stroke? It's like the second most discussed feature on the forums. And I'm really happy that the dev is currently working on it. I hope he's gonna manage to fix it along with some other frustrating bugs.
Please, begin to understand that when basic features are not working as expected (for years), blast of semi-useful features added in to market and sell the app to more people won't help the current userbase and will push unsatisfied people to voice their opinions. And they are entitled to do so. Not everyone is an uncritical fanboy. Some of us need to work, to rely on the tools we use.
Honestly - every time there's an update, I'm happy - hoping that most of the annoying bugs will be fixed. Instead, I get another bunch of regressions or new bugs.
It even seems that there are no testers in Serif.
Fyi, this is how was AD marketed to me:

That is true. Affinity Designer is young product, but it's not made by standards, and because of that I personally can't use it.
My shop accept Affinity user files, but for now only for printing (first i need to export them as tiff or something).
Just this step (rasterizing) defeat the purpose of owning it, and I'm sorry about that because I generally like product.
It's advertising precision, but it's simply not there when you need it (or be in standard to work).

Amount of nodes is crazy, and any devices cutter have limited amount of memory for cutting, and go crazy with stuff like that.
Just try to send that in any kind of production and you have a really big problem.
Just drop everything else and fix foundations of program, adopt it to standards and you're going to have one awesome product.

Yes, I know that they will announce when it's fixed, but for vector program this is unacceptable. I'm using CorelDraw to do my work (with Adobe CS6, SAi Flexi, and other specialized programs for rip/print/cut/engrave stuff), so I do not use Designer for serious work, but I bought it, and support it in my place of business. But this bug is now running joke. Vector program that is not precise is not good program, especially if your work depend on it. Even free programs that come with cutters nail this down (Graphtec, Roland, Gerber Omega...).
I hoped they did mitigate the problem with all other improvements they did (program is 400MB bigger in size then 1.6.1 version).
Also, you would think that you can bypass problem with this method, but I'm doing machine cutting, and regardless that you see clean line in Designer, it's broken at export (for other programs that follow standards it's unusable).
Look kind of OK, but it's not OK, not at all OK.

Just to report that Expand Stroke function still suck.
Check attached file, and zoom in first on top one, then on bottom.
 
CPP TEST.afdesign

Hi Elvys,
Welcome to Affinity Forums
Yes, we are listening and aware this is something that must be reviewed/fixed as soon as possible. Now that v1.7 of Photo and Designer are out as well as Publisher we should get back to regular updates/fixes soon. I'm sorry for the inconvenience this is causing you all. Thanks for your support/understanding.

Yes, I can... but did you see PDF export options in Designer (compare it to Illustrator/Corel)? My shop accept bunch of different formats, but PDF that you got from Designer is really not useful in production (sometimes RIP, sometimes just hang in cue/rip process), I just got broken print (that cost money).
When is Corel/Adobe (pre CC) PDF - it's smooth sailing.
Like I said, fix the curve/expand stroke glitch, make program follow standards, and they are fine
Corel did it, and all GNU/Linux stuff did it... and PDF is open standard.

That is true. Affinity Designer is young product, but it's not made by standards, and because of that I personally can't use it.
My shop accept Affinity user files, but for now only for printing (first i need to export them as tiff or something).
Just this step (rasterizing) defeat the purpose of owning it, and I'm sorry about that because I generally like product.
It's advertising precision, but it's simply not there when you need it (or be in standard to work).

Amount of nodes is crazy, and any devices cutter have limited amount of memory for cutting, and go crazy with stuff like that.
Just try to send that in any kind of production and you have a really big problem.
Just drop everything else and fix foundations of program, adopt it to standards and you're going to have one awesome product.

Just to report that Expand Stroke function still suck.
Check attached file, and zoom in first on top one, then on bottom.
 
CPP TEST.afdesign

Yes, I know that they will announce when it's fixed, but for vector program this is unacceptable. I'm using CorelDraw to do my work (with Adobe CS6, SAi Flexi, and other specialized programs for rip/print/cut/engrave stuff), so I do not use Designer for serious work, but I bought it, and support it in my place of business. But this bug is now running joke. Vector program that is not precise is not good program, especially if your work depend on it. Even free programs that come with cutters nail this down (Graphtec, Roland, Gerber Omega...).
I hoped they did mitigate the problem with all other improvements they did (program is 400MB bigger in size then 1.6.1 version).
Also, you would think that you can bypass problem with this method, but I'm doing machine cutting, and regardless that you see clean line in Designer, it's broken at export (for other programs that follow standards it's unusable).
Look kind of OK, but it's not OK, not at all OK.

Yeah, any kind of response/information about this subject from Affinity Designer team would be nice.

Yeah, any kind of response/information about this subject from Affinity Designer team would be nice.

Yeah, any kind of response/information about this subject from Affinity Designer team would be nice.

Yes, I know that they will announce when it's fixed, but for vector program this is unacceptable. I'm using CorelDraw to do my work (with Adobe CS6, SAi Flexi, and other specialized programs for rip/print/cut/engrave stuff), so I do not use Designer for serious work, but I bought it, and support it in my place of business. But this bug is now running joke. Vector program that is not precise is not good program, especially if your work depend on it. Even free programs that come with cutters nail this down (Graphtec, Roland, Gerber Omega...).
I hoped they did mitigate the problem with all other improvements they did (program is 400MB bigger in size then 1.6.1 version).
Also, you would think that you can bypass problem with this method, but I'm doing machine cutting, and regardless that you see clean line in Designer, it's broken at export (for other programs that follow standards it's unusable).
Look kind of OK, but it's not OK, not at all OK.

Just to report that Expand Stroke function still suck.
Check attached file, and zoom in first on top one, then on bottom.
 
CPP TEST.afdesign

Hi soloabner,
Welcome to Affinity Forums
No worries, better a duplicate than no report at all. As you noticed this is a known issue that's already logged with the devs. I have no idea if the fix comes with v1.7 but the dev team is well aware of it as it's been reported several times already.

I did one that I imagine is going to be "big but quick job" in Designer, oh boy, I was wrong.
All the fonts where big, really big (20 inch +), outlined. On screen look OK.
But then I exported all that out, PDF X3, EPS, SVG (cleaned background before export, so I don't have clipping, masking, etc.), font to curves. I try to open it (to check everything before cut) in Corel... it open the file, looks ok.
Turn on wireframe, and look it closely - and I'm screwed. Illustrator would not smell the file. Ok I try same thing in Flexi, and for some reason result is better, not perfect, but better. I remind you that font is 20 + inch, so small irregularities won't show - perfect.
Wrong again. It did not show on the screen, but in production sure did (I blame it on screen rendering in Flexi because it does not show smallest details). Lot of time and material vested, need to recreate everything in Corel. 
But let's think just a little bit.
You have font that's already vector by itself, and it show perfectly on the screen. You can parse it directly to vector. Then you have outline/contour of the font, that is also already perfectly good curve, why you do not just parse it in place?
Also I have feeling that Designer have 2 different "mesh" system. One for standard stuff, like fonts and images, and other one for curves. When you try to translate from one to another they probably have rounding errors. IDK.
Keep it stupid and simple.
My wife is visual artist, she is pissed when her art is changed in the way she did not intend to be changed .
WYSIWYG - that's how she roll