Anon223029

About the curves, Strokes, it's actually not too hard to get it right!
I obviously don't know the inner workings of Affinity's Software... therefore I'm not sure how complex
a fix of this can be. 
But since you find code written in JavaScript, doing this already decently... I kind of wonder.

http://mourner.github.io/simplify-js/
http://paperjs.org/tutorials/paths/smoothing-simplifying-flattening/#simplifying-paths
@MattP This brings up a different idea, wouldn't it be nice to be able to write little (let's say) javascript / python / etc expressions and save them as scripts/tools?
Similar to workflows you can find in 3D Software (Maya, Modo, Blender to name some). That would allow the community to fix these little issues. 

Sorry for the lack of response in this particular thread. I did mention in another Beta forum thread that I had been very busy over the last development cycle as I was writing the iPad version of Designer, so hadn't been able to spend time tackling a number of the most-requested features and bugs. I said in the other thread, so will re-iterate here that now iPad Designer is written, so I don't have to spend time developing that next cycle, so I can devote time to actually looking into these long-standing areas.
Also, I've got to say, there is no 'deafening silence' - there is a reality that we don't have a lot of developers and that you're actually talking to them on these forums - I can't type multiple things at once so when we're responding on here, we're not typing the features, so...

Just silence. Not a single ping … but … we got a new feature: bullets! 

28.July.2018. - another test - Affinity Designer 1.6.1 & Adobe Illustrator CC (22.1) (and for fun Inkscape 0.9.1 despite being unbearably slow on the Mac)
Somehow the 'Expand Stroke' issue isn't better. I didn't realise it's already over a year an issue.... good I didn't finish the font I was working on when I opened up the thread. 

+1 FIX THIS!

This is a long-standing issue that's been brought up time and again. I sincerely hope a fix sees the light of day eventually. In the meantime the only viable workaround is to take your path elsewhere (e.g. Inkscape), expand it and then bring it back in. Maybe it'll get promoted in the agenda if enough people voice their concerns so let's make some noise :)

28.July.2018. - another test - Affinity Designer 1.6.1 & Adobe Illustrator CC (22.1) (and for fun Inkscape 0.9.1 despite being unbearably slow on the Mac)
Somehow the 'Expand Stroke' issue isn't better. I didn't realise it's already over a year an issue.... good I didn't finish the font I was working on when I opened up the thread. 

28.July.2018. - another test - Affinity Designer 1.6.1 & Adobe Illustrator CC (22.1) (and for fun Inkscape 0.9.1 despite being unbearably slow on the Mac)
Somehow the 'Expand Stroke' issue isn't better. I didn't realise it's already over a year an issue.... good I didn't finish the font I was working on when I opened up the thread. 

That's my last on that topic.
Especially since it's two years ago that i faced that little problem.
 
I downloaded Adobe Illustrator CC (2017.2) as trial. And made the same tests, that pushed me to abandon it, with the current version.
And of course the one example expanded strokes in AI to Fontlab. 
 
1. Strokes are in AI are way way cleaner. Just have a look on the screenshot.
And when i copy it over, Fontlab recognises the path as well the expanded stroke keeps all editable.
This is how it should be!  kinda... 
 
2. AI has gotten faster,  finally. When i dropped it, I used the 2nd generation Retina MacBook Pro (16GB and Geforce GT750M, 2.3 Ghz Core i7...).
Illustrator had the tendency to slow down extremely (like 1fps) when tried to pan or zoom... or simply position and scale objects. Adobe back than said, I should avoid to work in 'retina' resolution when it slows down even lower the resolution! 
And that they are working on a solution. 2 Years later, now i own a iMac 5K and while AI is faster... --- like i might have 30fps when i pan the view.. let's say, it feels faster but not smooth.  
Working with it.. or loading the old documents that performed horribly - things are quite the same.  AI is very slow. It might be better but hardly noticeable. Must be the 5K. 
Maybe the old projects cause issues too...?! But even when i work on a new project its just not fast! = Funny when i open up the document in Affinity Designer its super smooth and even the old ones are super smooth.
That says something!  -- Still... I'm not happy with the expand stroke situation. 
 

Hi,
 
This will be coming to the next beta of Photo - so it should be in the App Store version in a couple of weeks..
 
It will let you shoot RAW directly using the camera - it will even shoot HDR brackets and merge them!
 
Thanks,
 
Andy.

Hilarious bug in the Affinity Designer 1.6 Beta 12
Happens when I use Mission Control on High Sierra 
Even more funny, the toolbar is still usable. :-)

@vwollschlaeger,
I think someone is very excited to use that 1,000,000% zoom feature.

Hilarious bug in the Affinity Designer 1.6 Beta 12
Happens when I use Mission Control on High Sierra 
Even more funny, the toolbar is still usable. :-)

Hilarious bug in the Affinity Designer 1.6 Beta 12
Happens when I use Mission Control on High Sierra 
Even more funny, the toolbar is still usable. :-)

Hilarious bug in the Affinity Designer 1.6 Beta 12
Happens when I use Mission Control on High Sierra 
Even more funny, the toolbar is still usable. :-)

Hilarious bug in the Affinity Designer 1.6 Beta 12
Happens when I use Mission Control on High Sierra 
Even more funny, the toolbar is still usable. :-)

Hey Matt, 
Thanks for the improvement to the Expand Stroke. This is just a simple test but so far I am liking what I see...
 
 

 
That is just a simple line drawn with the pen tool and a pressure curve applied. If I had to guess it would seem like the Expand Stroke command in 1.5.5 created almost 200 points whereas in 1.6 Beta 6 it may have created 20 points? It would be nice to have an Info panel of how many points an object has when you select it, manually counting it isn't fun!

That's actually a very good idea and would lead to more frequent usage !

First of all, many thanks for the new Light-UI - it helps much! I don't use it only under daylight conditions, it depends even on a picture, how bright it is. With the Light-UI and setting the Background Grey Level up, it is much more pleasant to work. But to change these settings individual for a picture it is less intuitiv to go every time to Preferences and chose the User Interface for a modification.   My simple idea and a big wish: Please make a placeable Icon for the Menubar which allows you to switch between Light & Dark with only one click. The arrow on the right side allows you to change the Background Grey Level with a simple fader like in the Preferences/User Interface. Isn't that much more user-friendly? : )      

@I'm a developer too, using macOS High Sierra actually against the common sense as daily driver.
I won't get into this philosophy ,... but you can create a new Document on 'High Sierra' with Affinity Designer/Photo by first clearing the User Data (starting Affinity Photo/Designer while pressing 'control') - after that you're able once dot create your document.
When you want todo another one repeat the steps.  --- that said... working with already existing documents works fine!

I think as this is a pretty important and core part of any vector application to get right, that the team are working hard to address this. 

Don't worry I didn't say the community is childish - I've meant they simply nag like kids that can't wait until the destination is reached.
I was a fun way to say: we need to be patient!

Hello Everyone,
Being a software developer / designer - ah... - multidisciplinary creative?! - creative developer (to avoid the hacky 'coder')
--- well --- you know?!  ;)
 
I don't understand that push for v1.6! - on one hand AF & AP aren't fundamentally broken...
in spite of few little things missing/not working properly, which is fine by it self, considering the age of the software..
 
Secondly, there is already a new macOS/iOS looming on the horizon. In fact, we all see June 5th,
'what will break' our software and needs to be ironed out until late-ish September.
 
APFS for instance ( due its case sensitivity - which by it self breaks for example all Adobe software ) - And trust me, APFS is a big deal! 
That's why i highlight that here. I don't care about it's security here that much, more about the end of data degradation!
For those, like me, having 30 years of data to preserve (I started coding at the age of 5, music composing around the same time)  
- i value that little detail quite a bit! -- just to have a real world example!
 
Point being.. 
Be excited, that these guys work hard, to provide a usable and more and more feasible alternative to Adobe/Corel/OpenSource software. 
Be more excited, about the time these guys, spend to experiment with actual new and innovate features or even just new touches on things that need to be re-thought. 
And don't forget they work still on Windows versions, as well iPad versions - and i'm not sure how much of their resources that takes.
 
Motivate the guys! Cheer to them! - And they will show/tease that way new ideas, perhaps even come up with innovative ways to incorporate feedback.
And stop behaving like kids ob the backseat of a car... nagging all the time when the trip is over (1.6 beta out < see the absurdity?!) and repeat even you've got what you wanted! 
 
Thanks for reading!
Happy designing...  let's make the guys proud.

Hello Everyone,
Being a software developer / designer - ah... - multidisciplinary creative?! - creative developer (to avoid the hacky 'coder')
--- well --- you know?!  ;)
 
I don't understand that push for v1.6! - on one hand AF & AP aren't fundamentally broken...
in spite of few little things missing/not working properly, which is fine by it self, considering the age of the software..
 
Secondly, there is already a new macOS/iOS looming on the horizon. In fact, we all see June 5th,
'what will break' our software and needs to be ironed out until late-ish September.
 
APFS for instance ( due its case sensitivity - which by it self breaks for example all Adobe software ) - And trust me, APFS is a big deal! 
That's why i highlight that here. I don't care about it's security here that much, more about the end of data degradation!
For those, like me, having 30 years of data to preserve (I started coding at the age of 5, music composing around the same time)  
- i value that little detail quite a bit! -- just to have a real world example!
 
Point being.. 
Be excited, that these guys work hard, to provide a usable and more and more feasible alternative to Adobe/Corel/OpenSource software. 
Be more excited, about the time these guys, spend to experiment with actual new and innovate features or even just new touches on things that need to be re-thought. 
And don't forget they work still on Windows versions, as well iPad versions - and i'm not sure how much of their resources that takes.
 
Motivate the guys! Cheer to them! - And they will show/tease that way new ideas, perhaps even come up with innovative ways to incorporate feedback.
And stop behaving like kids ob the backseat of a car... nagging all the time when the trip is over (1.6 beta out < see the absurdity?!) and repeat even you've got what you wanted! 
 
Thanks for reading!
Happy designing...  let's make the guys proud.

It was VERY unfortunate that Apple killed Aperture.
I like its superior UI (to anything else out there).
 
And I cannot understand why they had to kill it. 
Their cash flow is quite good.
Actually, the best on the planet...