Bug 408069 - If onion skin is on, the transform tool also includes pixels from the onion skin when calculating the boundaries
Summary: If onion skin is on, the transform tool also includes pixels from the onion s...
Status: RESOLVED DUPLICATE of bug 408152
Alias: None
Product: krita
Classification: Applications
Component: Animation (show other bugs)
Version: 4.2.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-29 13:42 UTC by stepan
Modified: 2019-07-04 02:52 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
The transformation tool covers the whole layer but not the active frame content (49.87 KB, image/jpeg)
2019-05-29 13:42 UTC, stepan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description stepan 2019-05-29 13:42:49 UTC
Created attachment 120372 [details]
The transformation tool covers the whole layer but not the active frame content

The transformation tool covers the whole layer but not the active frame content. 

krita 4,2,0 (x64) : Win 10 (x64) ,
Comment 1 Scott Petrovic 2019-05-29 13:51:29 UTC
Can you attach the KRA file to this bug post? Sometimes with things like this there is a semi-transparent pixel that is causing the bounding box to get larger like that. Not sure unless we can maybe see the KRA file
Comment 2 Scott Petrovic 2019-05-29 13:51:59 UTC
switching to needs info
Comment 3 stepan 2019-05-29 16:16:04 UTC
Oh, i gust found out that it happens  when  onion skin is turned on. If it is off , the transform tool works as usual.
Comment 4 Bug Janitor Service 2019-05-30 04:33:13 UTC
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.
Comment 5 Halla Rempt 2019-06-21 12:03:22 UTC
Setting to confirmed.
Comment 6 vanyossi 2019-07-04 02:52:44 UTC

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