https://bugs.kde.org/show_bug.cgi?id=461692
--- Comment #5 from keyth_qcfx2 <keyth2363...@gmail.com> --- As requested I tested it without Pigment.o installed in the system and it still does it, because all my testing was with Krita alone. To elaborate on why pigment is not in the way : Pigment.o was there in "read only" mode to assist me during this testing sessions. Also the released Pigment.o does not own any colors never did and can't and shouldn't (contrary to popular belief alot of the time). What it does is a redundancy check once, and once only. If the color spirals out of control is because Krita READ color is different from Krita WRITE color which means Krita did not pass the test with itself. Also the FG and BG color are treated independently so swapping within Krita would not cause update lag in Pigment.o as itself uses the Krita action to swap colors and then it just reacts to it. Adding to this version 2 (that I am using now) locks itself out of vectors because, vector layers haven't matched READ and WRITE for more than a year now. Before that vector layers were stable and everything was working. I have ignored this "pigmento bug" for a while since I would be correcting to probably to a Krita bug just to be reverted back again and having to redo it again, BUT alot of time has passed and no changes so I imagined it was really be a new way to do things with vectors. So I test to know how to do things ... But during my testing I just see it is just a collection of small bugs doing asynchrony that pass under the radar and not really a new way to do things as I was expecting now. So I report. -- You are receiving this mail because: You are watching all bug changes.
