Bug 376723

Summary: Non-selectable strings in layer blending modes
Product: [Applications] krita Reporter: Alexey <o-din13>
Component: Color modelsAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: minor CC: griffinvalley, nicholaslapointe8
Priority: NOR    
Version: 3.1.2   
Target Milestone: ---   
Platform: Mint (Ubuntu based)   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Non-selectable strings in layer blending modes
moving layers and reselect layers

Description Alexey 2017-02-20 17:52:41 UTC
Created attachment 104130 [details]
Non-selectable strings in layer blending modes

If we apply 'Separate image' function, we have non-selectable strings in layer blending modes. Try select other layer and all works again.
Comment 1 wolthera 2017-02-21 21:49:05 UTC
That's because the new layers are grayscale layers, you need to toggle 'output to color not grayscale' if you want all the blending modes to work.

I will close this bugreport now as it is not a bug.
Comment 2 Alexey 2017-04-25 10:28:38 UTC
(In reply to wolthera from comment #1)
> That's because the new layers are grayscale layers, you need to toggle
> 'output to color not grayscale' if you want all the blending modes to work.

 O'key... but all blending modes works correct if we simple reselect layer (no change a color space!). And layers color space is rgb, not grayscale. :)

 So, it's works but not works right after separation.

 So — it's a bug, not a feature. Minor bug but may be misleading.


P.S. I apologize for my awkward English, this is not my primary language
Comment 3 Alexey 2017-04-25 10:50:36 UTC
Created attachment 105182 [details]
moving layers and reselect layers

Yep! I be not correct, it's grayscale color space... but:

— Do you think this works correctly? ;)
Comment 4 Nicholas LaPointe 2017-04-25 11:37:08 UTC
In the second video you posted, it looks like applying "Separate image" leads to the same bug I noticed a few months ago. I'll mark this report as a duplicate.

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