Mercurial > MadButterfly

comparison include/mb_shapes.h @ 416:5791263ebe7b

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Document for why a shape should be managed by the redraw manager.
author Thinker K.F. Li <thinker@branda.to>
date Sun, 26 Jul 2009 15:31:40 +0800
parents 27774b93521e
children 9d5506968efb
comparison
equal deleted inserted replaced
415:fef1b8076041 416:5791263ebe7b
39 * 39 *
40 * All shape types must have a shape transform function. It is invoked by 40 * All shape types must have a shape transform function. It is invoked by
41 * redraw_man.c::clean_shape(). It's task is to update \ref geo_t of the 41 * redraw_man.c::clean_shape(). It's task is to update \ref geo_t of the
42 * shape object. In most situtation, it call geo_from_positions() to 42 * shape object. In most situtation, it call geo_from_positions() to
43 * update geo_t. 43 * update geo_t.
44 *
45 * \section rdman_man_shape Make a redraw manager managing a shape.
46 *
47 * It means managing life cycle of a shape to make a redraw manager
48 * managing a shape. Shapes are referenced by a redraw manager to
49 * update output device. So, a redraw manager must make sure all
50 * shapes are valid when they are needed to update output. To make sure
51 * lifecycle of shapes are synchronized with status of a redraw manager,
52 * lifecycle of shapes are managed by associated redraw manager.
44 * 53 *
45 */ 54 */
46 55
47 /*! \defgroup shapes Shapes 56 /*! \defgroup shapes Shapes
48 * @{ 57 * @{