https://bugs.kde.org/show_bug.cgi?id=518235
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from [email protected] --- This can happen with any document no matter how it was created. The number of blobs/marks or how they were does not matter as far as I can tell, only the location of the non-transparent pixels does. Pixels close to the bottom and right edges cause this, as do pixels anywhere off-canvas. I'm guessing Krita allocates data in chunks rather than pixel by pixel or for the entire layer, and when there are marks near the bottom/right canvas edge or off the canvas to the top/left, it allocates chunks that partially go off-canvas, and those off-canvas empty pixels are erroneously included when inverting the selection. I experimented with various canvas sizes, and it seems the extra pixels "added" in the inverted selection always pad the effective size to some multiple of a power of 2. On a 64x64 canvas, the bug does not occur unless pixels are placed off-canvas, I'm guessing because the allocated chunks exactly match the canvas size. (The chunk size seems to grow with the canvas size though, so just making the canvas a multiple of 64x64 is not enough to avoid this bug, it's likely there are only a few "perfect" canvas sizes.) (I'm on 5.3.1) -- You are receiving this mail because: You are watching all bug changes.
