diff options
Diffstat (limited to 'dw/imgbuf.hh')
| -rw-r--r-- | dw/imgbuf.hh | 30 |
1 files changed, 14 insertions, 16 deletions
diff --git a/dw/imgbuf.hh b/dw/imgbuf.hh index 8948bbef..150bf165 100644 --- a/dw/imgbuf.hh +++ b/dw/imgbuf.hh @@ -8,13 +8,11 @@ namespace dw { namespace core { -using namespace lout; - /** - * \brief The platform independant interface for image buffers. + * \brief The platform independent interface for image buffers. * * %Image buffers depend on the platform (see \ref dw-images-and-backgrounds), - * but have this general, platform independant interface. The purpose of + * but have this general, platform independent interface. The purpose of * an image buffer is * * <ol> @@ -53,16 +51,16 @@ using namespace lout; * * * <h3>Scaling</h3> - * + * * The buffer with the original size, which was created by * dw::core::Platform::createImgbuf, is called root buffer. Imgbuf provides * the ability to scale buffers. Generally, both root buffers, as well as * scaled buffers, may be shared, memory management is done by reference * counters. - * + * * Via dw::core::Imgbuf::getScaledBuf, you can retrieve a scaled buffer. * Generally, something like this must work always, in an efficient way: - * + * * \code * dw::core::Imgbuf *curBuf, *oldBuf; * int width, heigt, @@ -71,15 +69,15 @@ using namespace lout; * curBuf = oldBuf->getScaledBuf(oldBuf, width, height); * oldBuf->unref(); * \endcode - * + * * \em oldBuf may both be a root buffer, or a scaled buffer. - * + * * The root buffer keeps a list of all children, and all methods * operating on the image data (dw::core::Imgbuf::copyRow and * dw::core::Imgbuf::setCMap) are delegated to the scaled buffers, when * processed, and inherited, when a new scaled buffer is created. This * means, that they must only be performed for the root buffer. - * + * * A possible implementation could be (dw::fltk::FltkImgbuf does it this way): * * <ul> @@ -92,7 +90,7 @@ using namespace lout; * <li> Otherwise, if this buffer has already been scaled to the given * size, return this scaled buffer, with an increased reference * counter. - * + * * <li> Otherwise, return a new scaled buffer with reference counter 1. * </ul> * @@ -120,7 +118,7 @@ using namespace lout; * \code * dw::fltk::FltkPlatform *platform = new dw::fltk::FltkPlatform (); * dw::core::Layout *layout = new dw::core::Layout (platform); - * + * * dw::core::Imgbuf *rootbuf = * layout->createImgbuf (dw::core::Imgbuf::RGB, 100, 100); * dw::core::Imgbuf *scaledbuf = rootbuf->getScaledBuf (50, 50); @@ -133,12 +131,12 @@ using namespace lout; * the scaled buffer, it is deleted, and after it, the root buffer. * * <h3>Drawing</h3> - * + * * dw::core::Imgbuf provides no methods for drawing, instead, this is * done by the views (implementation of dw::core::View). * * There are two situations, when drawing is necessary: - * + * * <ol> * <li> To react on expose events, the function dw::core::View::drawImage * should be used, with the following parameters: @@ -149,7 +147,7 @@ using namespace lout; * <li> the region within the image, which should be displayed (\em x, * \em y, \em width, \em height). * </ul> - * + * * <li> When a row has been copied, it has to be drawn. To determine the * area, which has to be drawn, the dw::core::Imgbuf::getRowArea * should be used. The result can then passed @@ -158,7 +156,7 @@ using namespace lout; * * \sa \ref dw-images-and-backgrounds */ -class Imgbuf: public object::Object, public lout::signal::ObservedObject +class Imgbuf: public lout::object::Object, public lout::signal::ObservedObject { public: enum Type { RGB, RGBA, GRAY, INDEXED, INDEXED_ALPHA }; |