Pigment.O plugin

[Cerotonine]

Hello, first i’d like to thank you for making this plugin, i’ve been using it for more than a year at this point and it’s amazing. I wanted to let you know of a change that’s happened in krita 5.3 that’s affecting your plugin, i’ve been talking in another post with people on the forum about this, because at first i thought it was a modified version of krita we’re using but it’s something that happens with krita 5.3, it’s a change about how python plugins work that will make pigment.o need some rework or update. I’m not a coder so i don’t really understand exactly what’s going behind curtains, but this is what someone who knows his stuff is saying that’s wrong in krita 5.3:

@uvhat

Yes, issue is definitely caused by One more attempt to fix assert on node activation from Python (6c294f58) · Commits · Graphics / Krita · GitLab commit. I guess they decide to catch and await to execution of every user input from python, and plugin spams it too often. So Krita receieves changes from pigment.o, execute it and only after this try to work with next inputs. Previously, it simply skipped the outdated ones.

Author definitely should to rewrite logic of how Pigment.o interacts with Krita 5.3, it should not spam input events which this commit related, i guess.

This is actually a critical change, may affect for any other plugins for Krita. In one side it is important change, because previous builds could miss old user inputs from user plugins, with this change it execute full input and api calls queues from scripts. But the bad side is performance, if author didn’t make special efforts to manage queues order and didn’t limit rate of api calls.

I can try to make switch in settings, but it seems it will require to restart Krita to apply effect.

If it were possible, could you take a look at this and maybe implement some kind of fix?

Thank you for all your work on the plugin!