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

--- Comment #2 from Gavin Williams <[email protected]> ---
Step to reproduce...

1. Create a new image 128 x 128.
2. In the first 16 x 16 region (top-left), draw a white 4x4 box (bottom-left)
inset by one pixel in both x & y.
3. Select the 16 x 16 region.
4. Copy the selection.
5. Paste the selection.
6. Now move the selection so as to align the top-left of the selection box with
the top-left of the next 16x16 region to the right - This operation should copy
the first 16x16 region to the next 16x16 region, they should look the same.
7. See that the two 16x16 regions do not match, the white box is at the
top-left of the second 16x16 region. It's in a completely different position,
even though I just copied and pasted a selection and positioned it at the
top-left, so as to match the copy/paste regions.

If you suggest the solution is to manually line up the pasted object to match
the position of the copied object in its respective space, then you're missing
the point. The normal workflow would contain larger regions, with more detail,
where 1 pixel matters. I require consistency in the position of objects. And I
want the copy / paste operations to be oriented with respect to the top-left of
each sprite region. That's how I would position the copied objects in photoshop
or any other application. Krita disposes with the normal workflow and expects
me to manually reposition every object so that it matches the source position.
It's just annoying, and unnecessary, honestly, it's a block, I don't want to do
pixel work in Krita because of this issue. 

I'm not even sure what you're trying to prove with the workflow you enforce
here. Why do you presume to know that the user doesn't want those transparent
pixels that they selected. THEY SELECTED THOSE PIXELS. And you just throw away
parts of the selection. Why? Why do you think you understand my workflow better
than me? Are you trying to help me by throwing away my selection?

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

Reply via email to