diff options
| -rw-r--r-- | doc/dw-images-and-backgrounds.doc | 6 | ||||
| -rw-r--r-- | dw/style.cc | 4 | ||||
| -rw-r--r-- | dw/textblock.cc | 2 | ||||
| -rw-r--r-- | src/cssparser.cc | 2 |
4 files changed, 7 insertions, 7 deletions
diff --git a/doc/dw-images-and-backgrounds.doc b/doc/dw-images-and-backgrounds.doc index 6dfc7d79..f9a798cd 100644 --- a/doc/dw-images-and-backgrounds.doc +++ b/doc/dw-images-and-backgrounds.doc @@ -22,7 +22,7 @@ Image Renderer Generally, there are no restrictions on how to manage dw::core::Imgbuf; but to handle image data from web resources, the interface dw::core::ImgRenderer should be implemented. It is again -wrapped by DilloImago (to make access from the C part possible, since +wrapped by DilloImage (to make access from the C part possible, since dw::core::ImgRenderer is written in C++), which is referenced by DilloWeb. There are two positions where retrieving image data is initiated: @@ -78,7 +78,7 @@ renderers: - one instance of dw::core::style::StyleImage::StyleImgRenderer, which does everything needed for dw::core::style::StyleImage, and -- other renderes, used externally (widgets etc.), which are added by +- other renderers, used externally (widgets etc.), which are added by dw::core::style::StyleImage::putExternalImgRenderer (and removed by dw::core::style::StyleImage::removeExternalImgRenderer). @@ -223,7 +223,7 @@ dw::Image is only created with type RGB. This leads to several problems: 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; +The solution is basicly simple: keep alpha support out of dicache; instead implement RGBA in dw::Image. As it seems, the main problem is alpha support in FLTK/X11. diff --git a/dw/style.cc b/dw/style.cc index de9820eb..4ab5673a 100644 --- a/dw/style.cc +++ b/dw/style.cc @@ -611,7 +611,7 @@ void StyleImage::ExternalImgRenderer::drawRow (int row) if (doDraw) // Only iterate over y, because the rows can be combined - // horizontically. + // horizontally. for (int tileY = tileY1; tileY <= tileY2; tileY++) { int x1 = misc::max (origX + tileX1 * imgWidth, x); int x2 = misc::min (origX + (tileX2 + 1) * imgWidth, x + width); @@ -1154,7 +1154,7 @@ void drawBackground (View *view, Layout *layout, Rectangle *area, // image is set, and contents of <button> within a flat view, where the // background image of the toplevel widget is set), only the background // images are compared. A full test, which also deals with all other - // attributes related to backgrond images (repeat, position etc.) would + // attributes related to background images (repeat, position etc.) would // be complicated and useless, so not worth the work. (!atTop || layout->getBgImage () != style->backgroundImage); diff --git a/dw/textblock.cc b/dw/textblock.cc index a45b3da5..6a75dc96 100644 --- a/dw/textblock.cc +++ b/dw/textblock.cc @@ -87,7 +87,7 @@ void Textblock::WordImgRenderer::getBgArea (int *x, int *y, int *width, void Textblock::WordImgRenderer::getRefArea (int *xRef, int *yRef, int *widthRef, int *heightRef) { - // See comment in Widget::drawBox about the reference area.q + // See comment in Widget::drawBox about the reference area. textblock->getPaddingArea (xRef, yRef, widthRef, heightRef); } diff --git a/src/cssparser.cc b/src/cssparser.cc index 0d0ce5a1..e31c4090 100644 --- a/src/cssparser.cc +++ b/src/cssparser.cc @@ -1045,7 +1045,7 @@ bool CssParser::parseValue(CssPropertyName prop, // horizontal position; in most cases in this order. However, as long it // is unambigous, the order can be switched: "10px left" and "left 10px" // are both possible and have the same effect. For this reason, all - // possibilities are tested parrallel. + // possibilities are tested in parallel. bool h[2], v[2]; int pos[2]; |