[krita] [Bug 469109] Gradient dither adds dither to areas which are supposed to be transparent
https://bugs.kde.org/show_bug.cgi?id=469109 amyspark changed: What|Removed |Added Assignee|a...@amyspark.me |krita-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469109] Gradient dither adds dither to areas which are supposed to be transparent
https://bugs.kde.org/show_bug.cgi?id=469109 --- Comment #8 from tomtomtomreportin...@gmail.com --- Agreed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469109] Gradient dither adds dither to areas which are supposed to be transparent
https://bugs.kde.org/show_bug.cgi?id=469109 --- Comment #7 from Deif Lou --- Maybe it's just enough preventing the dithering on fully trandparent areas of the final applied gradient. My concern is that it may be some noticeable discontinuity where a fully transparent region meets a partially transparent one, but that's only speculation, it should be tested empirically. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469109] Gradient dither adds dither to areas which are supposed to be transparent
https://bugs.kde.org/show_bug.cgi?id=469109 --- Comment #6 from Raghavendra kamath --- I too was of the same opinion. I suggested for not adding the option on the IRC. but deif lour said that currently the colour in end point of the gradient is extended so if the gradient is from black to white the white is filled till the end of the canvas no matter where the user places the last end point. So by that logic krita extends the transparency till the end and that is why dithering is applied to whole canvas no matter where you end your gradient, since the fill is extended till the edge of the canvas. Hope I explained it correctly. If we end the gradient where the user places the last end point it would break the existing behavior of coloured gradient. We should check what other software do in this situation. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469109] Gradient dither adds dither to areas which are supposed to be transparent
https://bugs.kde.org/show_bug.cgi?id=469109 tomtomtomreportin...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 CC||tomtomtomreportingin@gmail. ||com Status|REPORTED|CONFIRMED --- Comment #5 from tomtomtomreportin...@gmail.com --- To be honest, making it an option rather than simply fixing the issue seems unnecessary. It's hard to imagine a usecase for dithered transparency side effects from a gradient, that requires a user to duplicate the layer mutliple times to even notice. Best to not overcomplicate things, in my opinion, unless someone really thinks it would improve their workflow (why not just use a noise filter if you want transparency dither?). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469109] Gradient dither adds dither to areas which are supposed to be transparent
https://bugs.kde.org/show_bug.cgi?id=469109 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Raghavendra kamath --- I think as deif lou suggests an option to ignore area with transparency would be good. It is okay to add dither to partially transparent area but not for fully transparent area. Also setting it to reported again since this will be closed by bug janitor in 30 days without any resolution. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469109] Gradient dither adds dither to areas which are supposed to be transparent
https://bugs.kde.org/show_bug.cgi?id=469109 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469109] Gradient dither adds dither to areas which are supposed to be transparent
https://bugs.kde.org/show_bug.cgi?id=469109 Deif Lou changed: What|Removed |Added CC||gin...@gmail.com --- Comment #2 from Deif Lou --- Would having 2 separate dithering options, for color channels and transparency help? That way the users can choose themselves, depending on they whant to achieve. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469109] Gradient dither adds dither to areas which are supposed to be transparent
https://bugs.kde.org/show_bug.cgi?id=469109 amyspark changed: What|Removed |Added CC||a...@amyspark.me Resolution|--- |WAITINGFORINFO Assignee|krita-bugs-n...@kde.org |a...@amyspark.me Status|REPORTED|NEEDSINFO --- Comment #1 from amyspark --- Hi! From a look at the original Inkscape code and my notes, I think this particular case was never expected or acted on. The testing was only done on fully opaque ramp gradients (which were the most affected). I'll raise the topic at tomorrow's meeting, but in the meanwhile, do you have any suggestions on how to handle partial transparency? -- You are receiving this mail because: You are watching all bug changes.
