diff options
author | Sebastian Geerken <devnull@localhost> | 2013-10-30 10:40:42 +0100 |
---|---|---|
committer | Sebastian Geerken <devnull@localhost> | 2013-10-30 10:40:42 +0100 |
commit | 1346a5fa9aa365e24724586adcb39746588712bf (patch) | |
tree | 898f84508b2933353bd8bc112e48252cc299e247 /doc | |
parent | 10934cb7dbb3eeaa30a9041228cf26c1c790bf5d (diff) |
Documentation.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/dw-images-and-backgrounds.doc | 15 |
1 files changed, 14 insertions, 1 deletions
diff --git a/doc/dw-images-and-backgrounds.doc b/doc/dw-images-and-backgrounds.doc index bf1eda27..caa08e8f 100644 --- a/doc/dw-images-and-backgrounds.doc +++ b/doc/dw-images-and-backgrounds.doc @@ -182,6 +182,8 @@ attached in StyleEngine::apply ("case CSS_PROPERTY_BACKGROUND_IMAGE"). Bugs and Things Needing Improvement =================================== +(Mostly related to image backgrounds, when not otherwise mentioned.) + High Priority ------------- @@ -224,6 +226,17 @@ as far as I see, no cache client is started.) Low Priority ------------ -None. +**Alpha support:** (not related to image backgrounds) currently alpha +support (and also colormap management) is done in dicache, while +dw::Image is only created with type RGB. This leads to several problems: + +- One dicache entry (representing an image related to the same URL), + which has only one background color, may refer to different images + with different background colors. +- The dicache only handles background colors, not background images. + +The solution is basicly simple: keep out alpha support out of dicache; +instead implement RGBA in dw::Image. As it seems, the main problem is +alpha support in FLTK/X11. */ |