Bug 411989 - Changing opacity percentage silder doesn't update on the brush preview.
Summary: Changing opacity percentage silder doesn't update on the brush preview.
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Brush engines (show other bugs)
Version: nightly build (please specify the git hash!)
Platform: Microsoft Windows Microsoft Windows
: NOR minor
Target Milestone: ---
Assignee: vanyossi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-17 09:36 UTC by acc4commissions
Modified: 2019-10-28 04:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description acc4commissions 2019-09-17 09:36:29 UTC 
SUMMARY
git 02bdc53

STEPS TO REPRODUCE
1. Open the brush editor.
2. Lower the opacity percentage silder of the brush.

OBSERVED RESULT
Brush preview shows no update.

EXPECTED RESULT
It should be transparent as the percentage decreases.

SOFTWARE/OS VERSIONS
Windows: Win7
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 vanyossi 2019-09-18 01:58:19 UTC 
Im sure this is intended by design as the preview is only purpose is to show an aproximation. For more precise preview of all the sensors you have to use the scratchpad area.
Comment 2 acc4commissions 2019-09-18 10:16:25 UTC 
(In reply to vanyossi from comment #1)
> Im sure this is intended by design as the preview is only purpose is to show
> an aproximation. For more precise preview of all the sensors you have to use
> the scratchpad area.

Is it? It becomes transparent when I decrease the flow percentage silder.
Comment 3 Ahab Greybeard 2019-09-18 15:24:21 UTC 
This happens with the pixel engine (and clone engine and tangent normal) brushes.

It does not happen for other brush engines that have opacity control, such as the bristle engine brushes.
Comment 4 vanyossi 2019-09-19 19:42:38 UTC 
In that case it is a bug.

confirming
Comment 5 vanyossi 2019-10-28 04:25:28 UTC 
This was fixed by scott by commit 56ee905262baa273