I use Krita to create diagrams and I use the Layer Styles > Gradient Overlay to colorize each diagram. I have a type of gradient that I use a lot, but every time I use it I need to tweak the stop positions slightly for it to work with the diagram.
It seems that Krita saves the gradients to a universal bucket such that when I tweak a gradient’s stop positions in one document, it affects that gradient in all the documents that use it.
One way I can get around this is to create a new gradient every time I want to use it in a new document, but then I would have dozens of similar gradients in my gradient selector, and I would have to name them all something unique.
I would like to be able to create/save gradients to the Krita document so that they are only associated with that file and do not appear in other files, similar to how palettes can be saved to the current document.
Additionally, it would be great to be able to duplicate a universal gradient and then save it as a document gradient, that way I can have a baseline gradient that all documents can access, which I could then quickly duplicate and edit to work for my current document, saving to the current document only.
Please, could you give us an image example, like a mock-up for visualizing the idea and how to be implemented into Krita UI or a example of this as a similar feature into another software.
Ultimately I don’t have a preference for how this might be implemented, but below is an idea of what could work.
On the gradient selection screen, when right-clicking on an existing gradient, there could be two additional options, ‘Assign to document’ to move the gradient from a universal one to one saved directly to the document, and ‘Copy to document’, that does the same thing but leaves the original universal gradient in place.
Is there any possibility of this feature being added? I’m surprised there aren’t others who would find this useful. Many of my gradients and other layer styles are unique to the document I’m working on, so being able to choose from the universal pool, edit them, and then save them specifically to the document would be a great workflow.
Then you should at least vote for your own request. It can be done on the left side of your headline when you scroll up to your first posting.
In my eyes I personally don’t need it. When I create a new resource, then I’ll create a backup of it immediately which then will be mirrored into the cloud too. In case of resources that aren’t saved into the document, I would ship them with the document, if I would want others to work on that file, which never happened so far. And if I’m the one, then I have it on disc and in the cloud. I don’t know if you constantly give away your files to others, which would make your request useful, or if you constantly switch your device, but at least I would either shipadditional files with my file or I knew where these are.
