There are a lot of possibilities, and quite likely affects more areas than I've thought of as yet. I would welcome any feedback about this suggestion. Chances are the changes to the current ramp algorithm would be minimal. This would also affect the ramp function in the palette editor, since it would need to accommodate colors with various alpha values and blend between them. Any suggestions in this regard are welcome. Another would be to replace the RGB and HSB with the alpha versions. One way would be to simply add versions with an alpha slider to the current pickers, that is, there would be Index, RGB, RGBA, HSB, HSBA, etc. ![]() The exact implementation of the color pickers can go in several different ways. Indexed color images would keep the current RGB color picker. For blur anyhow it could control how "strong" the blur effect is. This type of brush would be more useful for some of the ink types other than default, although to be honest I'm not entirely certain how some of them work in the first place. The current opacity setting could be rolled into a brush specific setting which would multiply the alpha of whatever color being painted by the opacity of the brush, so a color such as #ff00007f (red w/ 50% alpha) painted with a 50% opacity brush would paint #ff00003f (red w/ 25% alpha). The current method of using a separate opacity value (which could still be useful if thought of as "Brush Opacity" rather than the color alpha value) is somewhat clunky, and the color picker doesn't know how to pick up a semi-transparent color value. The internal pixel representation already uses RGBA, so most of this would merely be exposing that functionality within the user interface. It would also allow any feature which uses a color to use alpha values with out any extra work.Īs mentioned in issue #231, the hex codes would be 8 digits, #rrggbbaa, however it would be useful to construct the hex color string in such a way that colors with 255 alpha would be written as #rrggbb. Issue Partially Transparent Pixels #231 : Actually, this issue is basically asking for the same thing. ![]()
0 Comments
Leave a Reply. |