https://bugs.kde.org/show_bug.cgi?id=406764
--- Comment #8 from Larpon <dev.lar...@gmail.com> --- @Tymond yes of course. I guess this could be implemented as a plugin easily if we had functionality similar to GIMP's parasites. So via parasites on layers we could indeed have tag data stored in these parasites. Parasites is probably a bad name. It should probably be called meta- or simply, user data. But the concept is to allow plugin authors to store and retrieve (at least string) data on each layer which is saved with the project file. It would allow for plugins to store and operate on data across krita sessions, which a layer tagging solution would require. Right now I am personally resorting to base64 encoding in group layer names to store my data along with the document (krita-bulk-actions). Now if there was an official layer tag functionality in krita, plugins could adhere to that API and base functionality off of that. Thus operating on tags already available or sat by the user. If an official layer tagging API was available it could be used by other krita functionality to let the user target specific (tagged) layers to run operations on instead of having to manually select the same X layers everytime you need to apply a filter, color adjust, select from, copy from etc. I'm sure it could be used for much more. Right now I'm using my own plugin to switch multiple layers visibility and also to set opacity for multiple layers. I'm also using it to set the document in different "states" one state is often "export" where one button push allows me to set all the layer values and filters I want on before exporting. I have a similar "working" state set I can switch on and off, and also a "sketch/note" state that shows indications, notes or specific selections for certain areas. -- You are receiving this mail because: You are watching all bug changes.
