| Summary: | Fill with opacity actions (both FG & BG), do not yield the specified opacity | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | elkmug <elkmug> |
| Component: | Tools | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ahab.greybeard, griffinvalley |
| Priority: | NOR | ||
| Version First Reported In: | 4.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
elkmug
2020-07-03 20:33:46 UTC
I can confirm this for the 4.3.0 appimage and the Jul 06 4.3.1 alpha (git d3da61) appimage. It only happens with the Edit -> Fill Special item, not with the Fill Tool directly. The Jul 06 5.0.0 prealpha (git 193770b) appimage has different behaviour as follows: On first start, with a new image, the 'Fill with Foreground Color (Opacity)' gives 100% opacity fill. After that, for further layers and further new images, it gives about 25% opacity fills. I think this got fixed here: https://invent.kde.org/graphics/krita/-/commit/b869b46d88ff952124a189c7cd4f513f62d7222e can you check the next krita:plus to see if this is the case? (In reply to wolthera from comment #2) Tested with Krita Stable Windows Build #831 (krita-nightly-x64-v4.3.0-beta2-507-gaa84881e40) and can happily confirm this does fix the the issue :) Do I need mark this as 'resolved' or does that happen on the developer side? Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. Anybody can do it :) Tested with the Aug 08 4.3.1-alpha (git 4667f61) appimage |