Mercurial > MadButterfly

changeset 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 fef1b8076041
children abc420282c70
files include/mb_shapes.h
diffstat 1 files changed, 9 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- a/include/mb_shapes.h	Sun Jul 26 15:31:40 2009 +0800
+++ b/include/mb_shapes.h	Sun Jul 26 15:31:40 2009 +0800
@@ -41,6 +41,15 @@
  * redraw_man.c::clean_shape().  It's task is to update \ref geo_t of the
  * shape object.  In most situtation, it call geo_from_positions() to
  * update geo_t.
+ *
+ * \section rdman_man_shape Make a redraw manager managing a shape.
+ * 
+ * It means managing life cycle of a shape to make a redraw manager
+ * managing a shape.  Shapes are referenced by a redraw manager to
+ * update output device.  So, a redraw manager must make sure all
+ * shapes are valid when they are needed to update output.  To make sure
+ * lifecycle of shapes are synchronized with status of a redraw manager,
+ * lifecycle of shapes are managed by associated redraw manager.
  * 
  */