[1.8.0.555/585]AD opacity slider and appearance panel

[StuartRc]

Hi,

Thanks for the latest Beta..The new Document Panel is fantastic!

When testing the Expand stoke with multiple strokes (appearance panel)...I am getting a crash (locks up and needs Task Manager Closure!)
I was struggling to reproduce it at first as I thought it was a consequence of adding a 'vector' brush to the mix...but its not!..Its the opacity slider applied to a vector brush then expand or try to!

So with a bit of experimentation....just playing around with the options and mixing Styles + Multiple Strokes + vector brush applied to stroke to test extended feature of expand stroke

Reproduce
1. Create object..
2. Add Fill (I have used a pattern Style (as in resources)) (toggled)..and removed for testing (works really well so far!)
3. Add Vector Brush to Stoke
4. Change opacity with slider on the dropdown menu in appearance panel
5. App locks up

Tests
1. Add Stroke (change opacity)..Expand [works!]
2. Add Stroke without opacity change [works!]
3. Add vector Brush to stroke and change opacity then try to expand stroke... [fails!] 

NB
Works without the opacity change 
Attached a couple of simple files to play with
 

Expand stroke and brush.zip

[StuartRc]

Hi

Many thanks for the updates...thought I would see if this was occurring with the latest version.. and was not sure whether to add this as a new bug to latest release...but as there is no new beta yet..... and its already reported here...

I just tested this one with the latest released version today...unfortunately the issue is still present...

It is definitely the opacity slider on the fill option of the appearance panel that is causing AD to hang
 

NB.This time I tried it with adjustments to the fill not the stroke..and when you reboot AD the appearance panel  is no longer on the screen..

Process is logged in the file...
Changed the title of the thread

 

 

Stroke and appearance.zip

[Patrick Connor]

Sorry.

Thank you for reporting a problem using the pre 1.8.0 beta builds. It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. 

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

• Report a Bug in Affinity Designer
• Report a Bug in Affinity Photo
• Report a Bug in Affinity Publisher

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the release build.