Unnecessary take from my part
Yeah. Let’s me just:
Now for the meat and bones of my comment. I meant to ask yesterday about the ‘minor’ things about your first post. I just forgot and remember now.
Just writing the name of features don’t help much. Explaining in detail is helpful as can spark volunteers to start working, either on Krita’s code or in plugins to implement those.
Honorable mention
Krita liquify is cumbersome to activate. Having to always make the action: Transform Tool → Liquify Option
It is slow in a laughable manner. The quality of the resulting ‘liquified’ portion is lack-luster.
Liquify’s performance issue
Maybe we can make an overall to the UI/UX and code of the Transform Tool. Creating a feature request and discussing what is viable, and how to be done is the first step.
This is a CSP ‘docker’ with favorite actions and tools right? Then you can make different sets of favorites, is that right?
Not sure what you meant, especially when you said this is compared to PS. How is this compared to Krita?
Is Dual Brushes the same of Krita’s mask brushes?
There are options on CSP that Krita don’t have?
Does CSP work in a different way than PS and Krita Masked Brushes?
This one is the brush options in a ‘quick menu’ right? If yes. How does it work?
- Is the list of options general or per brush?
- If per brush what happen to a ‘newly created’ brush? There is a global set of ‘exposed’ properties in the window?
- It is similar to Krita’s Popup Palette, that appears on command and disappear when painting, or is more akin to a docker (always on screen)?