Changing Colour using Global Colours sets Tint back to 100%

[000]

1) create two global colours

2) apply Global Colour ONE to any object

3) Use the "tint" slider to set the colour to 50%

4) Select object and apply Global Colour number TWO

5) result: Colour is applied, tint is reset to 100%

Expected result: I did expect the colour to change but the tint setting to stay at 50%

[walt.farrell]

1 hour ago, Jens Krebs said:

Expected result: I did expect the colour to change but the tint setting to stay at 50%

I think your expectation needs adjusting, Jens

Tint (as opposed to Opacity) seems to be an attribute of the assigned color. Any change of the color (whether Global or not) includes changing the tint to however it's defined for that color.

[000]

28 minutes ago, walt.farrell said:

I think your expectation needs adjusting, Jens

Yes, possibly ... different software, different workflow.
Just wanted to put in here in case it actually IS a bug, because tint is handled differently in other software and I wasn't sure.
If it's by design, just close or delete this thread.

[thomaso]

Nevertheless, this thread might be almost ideally fitting as a reminder to that quite related issue:

This issue still occurs in v1.7.3 and current beta v518.

 

[000]

3 hours ago, thomaso said:

Nevertheless, this thread might be almost ideally fitting as a reminder to that quite related issue:

Looks like in your case the "tint" is separately from the colour (that's what I would prefer) whereas in my example the tint changes the colour -- anyways, the functionality seems to be jumbled up somehow. I keep my fingers crossed someone from Serif looks into this and it gets sorted out so that the tint works reliably the same in all three apps all the time.

[Patrick Connor]

Sorry.

Thank you for reporting a problem using 1.7.x . 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 current 1.8.3 release build.