Re: [Gimp-developer] Ctrl-clicking your way to a new layer mask

["draekko.software" <draekko software gmail com>]

On 12/31/2015 01:20 PM, C R wrote:
> > On 12/31/2015 09:51 AM, C R wrote:
> >>
> >> Looks cool.
> >> Although I like the idea of being able to modifier-click on the 
> layers, I worry that when layers become multi-selectable in GIMP, the 
> ctrl-key may be better used to toggle-select individual layers (shift 
> being used to select a sub-section of layers). This is the convention 
> used in most browsers and other programs. Maybe try the alt key as a 
> modifier instead of ctrl?
> >>
> > No it wouldn't interfere as you need to click on the image same as 
> you do for the layer mask to select either you'd only be adding 
> functionality to it.
>
> Your video shows Ctrl-clicking on a layer. Intuitively I'd expect this 
> to add the layer to the selection of layers, not create a layer mask. 
> Clicking on an already selected layer should deselect it using this 
> convention. This is why I recommend alt instead. It's less likely to 
> get in the way of multi select operations, which GIMP will no doubt 
> acquire eventually.

I guess whoever gets to commit this to git can make that call (alt or 
ctrl), though i personally would prefer it to ctrl.

> > Easy as i've explained before so many times, when you have have too 
> many applications opened at the same time all competing for shortcuts, 
> i already don't have enough keys to accomodate all them as is.  Maybe 
> you don't have that issue but i'm hardly the only one in that situation.
>
> Yes, I can't say that I envy that situation. Sounds like a mess! :) I 
> have set up 10 system-wide shortcuts, and all of them are 
> ctrl-alt-shift modifiers specifically so I don't run into conflicts. I 
> use very hotkey heavy applications such as Blender 3D daily, so any 
> software that required global hotkeys conflicting with GIMP, Blender, 
> Inkscape etc. would get removed pretty quickly.
>
> Rather than adding mystery functionality to ctrl-clicking, perhaps 
> addressing the cause of your hotkey problem would be better in the 
> long run?
>
> That's what I would do anyway. :)

That's great for you, can't do that here.

Ben