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 569487 - The effect of deactivating RGBA channels in the channels dialog can be described better
The effect of deactivating RGBA channels in the channels dialog can be descri...
Status: RESOLVED OBSOLETE
Product: GIMP-manual
Classification: Other
Component: English
git master
Other All
: Normal normal
: ---
Assigned To: Róman Joost
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2009-01-28 17:58 UTC by Michael Schumacher
Modified: 2018-05-24 10:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Schumacher 2009-01-28 17:58:30 UTC
http://docs.gimp.org/en/gimp-channel-dialog.html

The is a Caution! box that tells the readers a tiny bit about the effects of deactivating channels, but this is IMO not enough to grasp what's going on.

Things that should be mentioned there:

1. Deactivating RGBA components does not change the way tools work

 A brush will continue to paint as usual, changing the pixels of the layer you're working on. The eraser will change the alpha value of the pixels you're working on, ect.

2. Activated RGBA components decide which part(s) of a tools action is applied to the layer 

Painting black in normal mode on a fully opaque layer does not make the layer go transparent even if the only channel you've activate is the Alpha one - the paintbrush does just not do this - and using the eraser will not change your image if the alpha channel is not active.


Conclusion: the RGBA channels are there to provde a way to changes (that would happen anyway) to the layer components, they are not designed to redirect changes to the activated components.
Comment 1 Michael Schumacher 2017-02-28 20:44:26 UTC
qa contact change to bugs@gimp.org
Comment 2 GNOME Infrastructure Team 2018-05-24 10:26:38 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp-help-2/issues/7.