Bug 317829 - psd import does not properly support layer groups
Summary: psd import does not properly support layer groups
Status: RESOLVED DUPLICATE of bug 289857
Alias: None
Product: krita
Classification: Applications
Component: File formats (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Siddharth
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-04 14:50 UTC by Danni Coy
Modified: 2014-05-23 12:00 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Danni Coy 2013-04-04 14:50:22 UTC
Is it possible to have transforms on a layer group - if so it is important to have this implemented.

Reproducible: Always

Steps to Reproduce:
1. Open a psd file 
2.
3.
Actual Results:  
(look at the the difference between the attached file as a thumbnail in dolphin and open in krita) 

Expected Results:  
see above
Comment 1 Danni Coy 2013-04-04 17:58:41 UTC
I was going to send a sample file - but it a lot bigger than I was expecting and will take forever to upload
Comment 2 Halla Rempt 2013-04-23 08:47:13 UTC
Hi, there is one tricky bit here: photoshop groups and krita groups are quite different beasts. In krita layers inside a group are first composited together, then the result is composited in the stack. In Photoshop, groups are more like tags that are shown visually, but the stack is still linear.

We can solve this by adding tagging to our layers in Krita.
Comment 3 Bollebib 2013-04-26 20:33:24 UTC
this would be useful to me as I sometimes am forced to resort to psd's with clients. Neither gimp nor krita can handle them effectively. It's a major plus for people who would like to switch over I imagine,but can't.
Comment 4 Camilla Boemann 2013-12-02 07:59:07 UTC
there is some overlap with https://bugs.kde.org/show_bug.cgi?id=289857 which i'm looking at.

Will test this bug once i'm done with the other
Comment 5 Halla Rempt 2014-05-23 12:00:52 UTC

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