https://bugs.kde.org/show_bug.cgi?id=381296
Bug ID: 381296
Summary: Selecting Move Tool leaves a print of the edges behind
Product: krita
Version: 3.1.4
Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: transform
Assignee: krita-bugs-n...@kde.org
Reporter: zsomkov...@gmail.com
Target Milestone: ---
Created attachment 106129
--> https://bugs.kde.org/attachment.cgi?id=106129&action=edit
Prints of edges after selecting Move Tool
Steps to reproduce:
1) Create a new, blank Image
2) Select an arbitrary area with either the Elliptical Selection Tool,
Polygonal Selection Tool or Outline Selection Tool
3) Use the Fill Tool to fill the selected area with any chosen color (for more
visible results, use darker colors)
4) Select the Move Tool
5) Either move the selected area or press delete to remove the contents of the
selection
Expected behaviour:
The canvas is blank at the place of the original selection, or completely, in
case of deletion
Actual behaviour:
There is a print of the edges of the selected area at the place of the selected
area
-----
Notes:
- The bug can be reproduced with either the integrated Intel graphical
accelerator (7th generation Core i5 CPU) and an Nvidia GPU (950M, 960M tested).
Both PCs ran Windows 10 Professional x64, using Krita x64 or Portable x64
edition. I did not check any of the Linux nor the OSX distributables.
- The bug can be reproduced from at least the 3.0 Portable version (I could not
find 2.8 or 2.9 Portable editions) and it is still reproducible in the 4.0.0
pre-alpha (unstable repository).
- Enabling or disabling OpenGL display did not affect the problem in any way.
- Using either Pixel Selection or Vector Selection mode for the selection tools
does not affect the problem in any way.
- The bug can't seem to be reproducible by using the Rectangular selection tool
at all, the three selection tool listed above always results in the descripted
behaviour.
- Since the descripted behaviour occurs even when deleting the selected content
without moving it at all, it is unlikely that the problem is related to the
actual movement of the layer, I feel like it has something to do with the Move
Tool initialization.
-----
Similar known problems:
- It is probably related to Bug 350263
(https://bugs.kde.org/show_bug.cgi?id=350263), the result on the attached video
is quite similar to this one, but it uses another tool to achieve this
behaviour.
--
You are receiving this mail because:
You are watching all bug changes.
