v149: Color picker and Brush anti-cooperation

[IPv6]

There is really annoying problem with color picket and brush tool. Color picker presumably should pick active color, that can be immediately used with brush (or any other) tool.
But switching from picker to brush always exchange just-picked-color with previous color, effectively killing effort for picking color... see attached video.


N.B.: alt-picking with brush works well, but picker has some advantages when used in isolated editing - alt-pick always pick "top level" color (which is usually not helpful), where color picker can be used to pick color from active layer... so color picker is more usefull, except that strange behaviour you can see from video

 

 

[TomM1]

This is normal behavior, not just the beta.

It requires an extra click to go back and set the bush to the picked color.

[IPv6]

i know about X button, but still... This is weird behaviour, imho, not normal. Color picker exists to pick color for brush (among other uses).
May be better to move this topic into feature requests, though...
 

[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.