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 320140 - brush painting broken with locked transparency
brush painting broken with locked transparency
Status: RESOLVED DUPLICATE of bug 307213
Product: GIMP
Classification: Other
Component: Tools
git master
Other All
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2005-10-29 00:05 UTC by Jakub Steiner
Modified: 2005-10-31 15:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jakub Steiner 2005-10-29 00:05:00 UTC
Please describe the problem:
The lock transparency functionality exposed in the layer dock UI is used to
limit the paining operations to the alpha-opaque areas of a layer. Using pain
tools (pencil and paintbrush) recently stopped behaving the way it used to. 

Steps to reproduce:
1. create a new empty layer
2. create a circle selection and fill with grey, select none.
3. pick a 1x1 brush, select black fg color, pencil tool and set the brush
opacity to 40%
4. try painting. everything works as should.
5. lock transparency of the layer (set lock alpha channel checkbox in the layer
dock)
6. try paining again. the painting should be limited to the contour of the
circle, but it should look the same as in step 4. 

Actual results:
You get a 4x4 fully opaque brush painting. this is especially evident
misbehavior with the paintbrush tool as it's otherwise anti-aliased but with
alpha locked, it isn't.

Expected results:
The paininting should look the same as without alpha locking, but limitied to
the layer's alpha-channel defined contour.

Does this happen every time?
yes

Other information:
this is cvs head.
Comment 1 Jakub Steiner 2005-10-29 00:05:27 UTC
a demonstration at http://jimmac.musichall.cz/demos/gimp/gimp-wtf-brush.avi
Comment 2 weskaggs 2005-10-31 15:00:34 UTC
Yeah -- we already know about this, thanks.



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