https://bugs.kde.org/show_bug.cgi?id=415788

Ahab Greybeard <ahab.greybe...@hotmail.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
         Resolution|WAITINGFORINFO              |---
                 CC|                            |ahab.greybe...@hotmail.co.u
                   |                            |k
             Status|NEEDSINFO                   |CONFIRMED

--- Comment #2 from Ahab Greybeard <ahab.greybe...@hotmail.co.uk> ---
This happens in all versions from 4.2.6 onwards in the Linux appimages and the
Windows portable .zip packages running on Windows 10.

It's best observed with a single paint layer with a transform mask on it.
I suggest a filled rectangle on the paint layer and a simple 45 degree rotation
transform mask for intial investigation.
(If you use a mild perspective transform, there is severe distortion of the
moving object and some large artifacts are created.)

It happens when you use the Move tool on the paint layer with Instant Preview
Mode enabled.
(If Instant Preview Mode is disabled, the moves happen normally but there is
break up of the paint layer object during the move as may be expected.)

On my Linux system, it only happens for images that are greater than 1191
pixels in either side. Below that size, the move behaves well. (This number may
be particular to my system, I don't know.)
Above that size, there is an immediate offset of the paint layer object that
persists throughout the movement.
When the move is finalised, by Return, the object goes to where it should be
and leaves an artifact copy on the canvas at the offset position.
If you don't finalise the move, then the object goes to where it should be
after a 4 second wait, leaving an artifact behind.

The artifact can be removed by turning the background layer off then on again.

On Windows 10, there is an image size limit but it's different and I haven't
tracked down the exact value.
For large images (2048 x 2048) it's the same as on Linux.
For small images (1024 x 1024), it can behave strangely with horizontal cursor
movement giving vertical object movement and vice-versa but this is not
consistent.

After repeated moving around on a small image Windows session, I had a crash
that did not leave a record in the crash log.

Setting to Confirmed

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to