ah yes, I wasn't expecting it for 2.9 or even 3.0

I was just curious, thanks for the response.

I like a lot the last proposal, from kamathraghavendra.

My opinion about the "inherit alpha" icon:
First I must correct, when scottpetrovic said "the layer will pick up all of the below layers when determing the painting region (similar to the transparency lock)".
That is not exactly what it does, and is quite different from alpha lock. The layer doesn't pick anything. You can still paint anywhere on the layer, it's just that the way the layer is composited, its alpha channel is disabled and so not modifying the alpha in the compositing stack. So that is only a shortcut, exactly the same as going to layer properties and disable the alpha channel (which is the old way/another way to do it for paint layers, and still the only way to do it for other types of layers.. I tried to add the shortcut to other layer types for consistency but never went far enough..).
By the way I must say again I don't think that's a good idea to have renamed it to "inherit alpha", that makes two different names for exactly the same thing. That is only bringing confusion to people about what it does.
So in the same idea I believe adding some kind of arrows to the icon will increase this confusion.

@Animtim -- It sounds like you understand that feature better than most people. I originally tried learning about it through here.

https://userbase.kde.org/Krita/Tutorial ... parency.29

It is called "Inherit Alpha" there, so that is why I was calling it that. My understanding is based off what I read. Please update that page if it is incorrect. Based off your description on what it does, it sounds like that icon should be called "disable alpha channel".

It does seem like an obscure feature. Is it really important enough to show as an icon on every layer? Are there any good tutorials or guides with the different use cases for it?

Héhé, actually in a few days I'm about to start releasing some up to date documentation as part of my work, and so I'll probably update the wiki entry based on it. The layer stack is my next item to write, so it'll be released very soon... but don't say it too loud, I didn't announce it yet

As for this icon name, it was originally named "disable alpha channel", only recently it's been changed to "inherit alpha" for some reasons, but I would also prefer to keep the original name if enough people agreed about this..

This is how I think layerbox should look like.
Visible and lock icons should be always on first place because you have them for every type of layer. Also this allows you to turn on/off more icons quicker.

I like those icons
But the proposal for the layer stack does not include a view of layer groups trees, which is very important even more when working with nested groups.
Could you try to include that in your mockup?

Animtim wrote:I like those icons
But the proposal for the layer stack does not include a view of layer groups trees, which is very important even more when working with nested groups.
Could you try to include that in your mockup?

Thank you @Animtim, sorry for delay. By the way, I sent you an email a few days ago about new icon set
For the layer group trees, I will make mockup when I catch free time.

Mockup with layer groups trees.

I see you included a group-layer view, good. But it shows only one level of group, while it's very common to have nested groups, sometimes several levels (a group inside a group inside a group..)
so we need to make better use of the horizontal space. Considering this, I think the two big buttons on the left as those on the right take way too much space this way.

BTW, guys, I think it would be good to understand that QT, our base for the UI, is themable.

Particularly, the enviroment Krita was made for, KDE, prides themselves on themability. This is important when considering mockups and wireframes.

To wit, if you are a windows user, you have by default the plastique theme.

On Linux, by default, you use Oxygen:


However, if you have KDE plasma 5, you will see Breeze:


As you can see, they look pretty different(if only because mmolch, whose screenshot that was, has disabled the title-bars of dockers.), I imagine that'll have much effect on how you design your dockers

I don't know how complex it is to get a KDE theme onto windows or the like, but do try to think in terms of something looking nice in plastique as well as oxygen and breeze(or other QT themes)

another interesting detail is that our layer docker can show the layers in 3 different layouts:



Though, I am seeing that the tumbnail view doesn't have toggle icons... I wonder why?
Also interesting is that the minimal view has the icons aligned to the right, with the hierarchy on the left. However, the visible icons, I think, would benefit from being right underneath each other, because this seems like it created a lot of missclicks.

That said, we have phabricator where you can create so called 'pholio' items, so that you can upload your ideas and attach them to this item, instead of letting them be ruled by myterious image uploaders on the internet

https://phabricator.kde.org/T106 < This is the task for the layerdocker.

To login, use you forum account in the LDAP account area.