After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 101971 - Add "Mask" mode for layer compositing
Add "Mask" mode for layer compositing
Status: RESOLVED DUPLICATE of bug 51112
Product: GIMP
Classification: Other
Component: General
1.x
Other Linux
: Normal enhancement
: ---
Assigned To: GIMP Bugs
Daniel Egger
Depends on:
Blocks:
 
 
Reported: 2002-12-26 01:59 UTC by Craig Lawson
Modified: 2003-01-06 17:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Craig Lawson 2002-12-26 01:59:05 UTC
A suggestion: Add "Mask" mode for layer compositing. "Mask" mode would
affect the alpha layer of resulting image. Full white in the current layer
would multiply image's alpha by 1.0 (identity function), and full black or
alpha=0 would multiply the image's alpha by 0. Gray values would make
portions of the image transparent.

This functionality would be similar to "Layer Mask", except that a layer
mask applies to only one layer. A "mask" layer would apply to all layers
below it in the stack.

Currently, the layer modes do not affect the alpha channel of the resulting
image: the new alpha is always an additive combination of the current layer
and the one below. "Mask" mode would add similar flexibility in
manipulating the alpha layer as exists for manipulating the images, value,
RGB, or HSV.

Work around:
Define a layer mask and apply to all layers that require masking. Changing
the mask is a pain, however.
Comment 1 Raphaël Quinet 2003-01-06 17:51:56 UTC
This is a duplicate of bug #51112: it describes a feature that allows
you to define a layer as a "clipping mask" that affects a "clipping
group".  The clipping group is a group of layers that are affected by
that mask.  This feature is available in Photoshop; more details are
given in some of the comments attached to that bug report.


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