@novames00 you need to familiarize yourself with gamut masks first, then, before making a feature request duplicating the functionality. If you familiarize yourself with it, you’ll know the exact issues that are there (because there are ones, of course, like with everything else) and you’ll also be able to suggest specific changes to the current design that are actually actionable. For example, the gamut masks are resources, like brush presets or palettes - they need to still be treated like that, otherwise it would be cutting off existing functionality for pretty circles around the color selector.
The name of the game is “incremental improvement”. We cannot just throw out one feature to implement a new one with slightly different functionality only because the new one is more comfortable (it’s wasteful - development takes time!). Instead, we need to find ways to make the old one comfortable (unless it’s really really broken by (code) design - but gamut masks aren’t).
So, if you have a feature request, it must be built upon the existing functionality. Showing off a feature in some other program that achieves roughly the same that is already available in Krita is not a good feature request.
Imagine if someone actually listened to you and implemented exactly what you ask for here. Then Krita has two ways of achieving the same thing. Later someone posts a screenshot from, let’s say, Procreate, or maybe Corel Painter, which has just another way to achieve color harmony. Someone says “great, that’s a terrific feature request!” and implements that one too… and then Krita would have three ways of doing the same thing. Every one more comfortable than the previous one. Doesn’t it sound like wasting developers’ time? And confusing new users?
Treat the amazing features you find in other software as inspiration, not reference. And make feature requests for Krita - built upon everything that Krita already has. If gamut masks are inconvenient to use right now, figure out how the UX can be changed so they will be convenient, and make a feature request for that.
For example, this was a very good feature request: Mockup: perspective tool - David Revoy - this was written ten years ago, as you can see. It’s amazing: it has images, detailed description, workflow is explained, perfect feature request for a big feature. However, if David wrote it today, it wouldn’t be a good feature request anymore - because it doesn’t take the fact that there has been work done on assistants, especially the new 2pp assistant (will come in Krita 5), into account. So while it was good ten years ago, today it lacks context. It can only be an inspiration to what’s needed in the new 2pp assistant. And the same goes for any feature from any other program. (And remember that Krita is allowed to have features actually better than other programs, not just copies of their features!)
