All uncertain features go in here, if they're still there after a year, they'll get deleted.
Fri, Jul 12
Thu, Jul 11
Jun 13 2019
- There's already the "touchdockermapping" kisconfig entry that should make it possible to store and restore mappings.
- I intentionally did not want to offer an alternative button layout, because this was mimicking the buttons on a wacom cintiq, more or less
- no idea about that
Jun 7 2019
Spot color discussion on Libtiff ML (Same thread, different archive software) :
Notes on the meeting with Jan-Peter Hohmann from Freie Farbe (https://www.freiefarbe.de):
Jun 4 2019
May 10 2019
Disclaimer: I never used the Global selection mask, and I discovered the feature 5min ago, on the Select menu.
So here is my feedback:
May 4 2019
Apr 30 2019
The option is already present in Krita in Selection->Show Global Selection Mask menu:
Apr 29 2019
Apr 21 2019
I have made a separate dialog for this purpose. Merging it into Layer Properties is possible, but it could possibly mess up with the ui file, since most of the properties of general layers make sense to Clone Layers (this also holds for File Layers, so actually some settings of File Layers are made more difficult to change).
Apr 20 2019
I think a separate dialog for selecting would be the most convenient for the users (option 2). And @vanyossi's idea about merging this dialog with the layer properties is very good. Actually, properties dialog is the most obvious place for the users to search for this option. Though it might be not very easy to add switchable options to it. I guess we could add a pager-widget to it and add pages for custom options like for clone layers and file layers. Though it will be quite a bit of work.
Making the option available in the "Layer properties" pop-up is the most intuitive for me. But don't remove all the other options as the "file layer" pop-up does, add to the extra field to the popup instead in case is clone layer :)
Apr 19 2019
Pop-up dialog would be consistent with the behaviour on file layers, and I imagine also the least sensitive to bugs.
Apr 18 2019
Mar 19 2019
Mar 16 2019
Mar 12 2019
This one was resolved at the during the 4.0 bugfix phase.
The layer docker uses squeezed combobox now.
Mar 5 2019
Mar 4 2019
Feb 1 2019
the "creamy effect" selected by default nice , then i agree to integrate it in preferences.
New users are not even worried about these variants. They look for the "Patched mode" based on another softwares experience.
Happy to see this is evolving ;D
Referring to Deevad last comment showing the prefs with patch, i don´t see
this as a need. After testing a lot, the "flow changed" release, for me it
is better, and keeping an older version can be more confuse more new users.
I've just pushed William's patch into master. The new mode can be configured globally in Krita settings (it is on by default).
Jan 25 2019
Hi, picture on top: I ran tests to compare 4.1.5appimage (left) and git~master with the flow patch (right).
Jan 23 2019
I agree with everything said here. I think is good for Krita to fit the standards when we are talking about basic features. So for me is a good oportunity to fix something we have used to ( a bit weird in some cases).
Breaking something that a user has created (custom brushes) is dangerous. i agree with @Deevad worries.
And also agree with @kamathraghavendra we have to take in mind the manual too and not loose coherence between what the softwares do and what the users read when they are learning.
This patch looks very good! Though +1 that it needs a solid update plan...
As deevad said, thank you very much for this patch, and from initial testing it seems to be a desirable change. However as deevad said, all the brushes needs to be changed to incorporate this new behavior and also we need to update the documentation stating this change. We need a proper plan to roll out this change.
Thank you for taking care of this (huge) issue, the screenshot looks really promising.
Okay, done :)
Cool that you managed to make a patch! You can submit it by making a review request(press the star in the topright next to your name). You will need to select krita as the repository, and as the reviewers, and you'll need to point them at this task and the forum thread so you don't get a confused reviewer.
I'm not sure if I should put this here, or on the forums, but after looking at it for a bit, I think I've found the root of this bug. It's mostly caused by a problem in the Alpha Darken Composite Op, and fixing it only involves changing a few lines of code.
Jan 7 2019
I guess it just wasn't finished and worked only in few cases... and caused regressions in other cases
Jan 6 2019
This is an updated diff against krita/4.1 for the dithering work:
So... Does anyone remember why this wasn't merged?
Dec 11 2018
Dec 2 2018
Hi pilee, can you please report this to bugs.kde.org, we only use phabricator to discuss things(as it is really good at that), but not to track our bugs and todolists(as it isn't that great at that part).