Bug 219766

Summary:	Resizing an image messes up shape layes
Product:	[Applications] krita	Reporter:	Thomas Zander <zander>
Component:	General	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	halla
Priority:	NOR
Version:	2.1
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Thomas Zander 2009-12-23 00:22:18 UTC

2 bugs that seem to be the same thing, so I'll restrict myself to one report;

* open an image and insert a circle shape.
* change resolution of image from 72 to 96dpi.

I expect the shape layer to be re-rasterized. Instead I notice that the old contents is kept. You can select the circle and move it slightly to trigger a re-rasterization.

2nd bug.
* open an image and insert a text shape.
* change the image size to be 50%.

I expect the resizing of an image to have no effect on my shapes. Instead, my shapes suddenly got twice the size.
What about making the resizing auto-adjust the DPI ?

Comment 1 Sven Langkamp 2009-12-23 12:38:35 UTC

Was fit to page activated in the second case? That would explain why the shape appears bigger.

Comment 2 Sven Langkamp 2009-12-23 15:00:02 UTC

Confirming the first bug. Seems that the shape layer compositing is wrong after some operations.

Comment 3 Thomas Zander 2009-12-23 20:45:31 UTC

re #1; yes it was enabled.

My reasoning for saying this is a bug is essentially the following logic;
I take a picture and position flake-content on top.  The flake content are positioned and sized based on the pixel content. (thats why I choose to do this in Krita).

When I resize an image (less pixels) I expect *all* content to get smaller, and at the same amount.  In other words; I want the positioning to be preserved.

So, the default setting to not touch the DPI when I resize to 50% by removing pixels is wrong.  As it breaks the above usecase.

Comment 4 Sven Langkamp 2009-12-28 20:31:02 UTC

2nd is fixed now. The first bug is still there.

Comment 5 Halla Rempt 2010-03-02 09:33:16 UTC


*** This bug has been marked as a duplicate of bug 227512 ***