Comment 3 for bug 285966
Revision history for this message
| Guillermo Espertino (Gez) (gespertino-gmail) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Another report about a misinterpretation of the style inheritance feature: #358563
Inheriting opacity in new shapes seems to make more harm than good.
I think a fast and elegant solution would be to disable it as default and make it available via preferences.
I mean, color and stroke can be inherited, but the user should have to explicitly activate the opacity inheritance in features to get it.
That would eliminate the recurring bug report about tools that have not effect and disappearing objects. Or, in this last case I mention, about "pale" objects.
Of course it's ok to inherit opacity when pasting the style in another object, but inheriting it in new shapes proved to be quite problematic.
Again, I'd change this to BUG.