Mercurial > MadButterfly

comparison src/redraw_man.c @ 141:e89512d6fa0a

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Change doxygen comment to reflect changes of relation-ship. Relation-ship among coord, geo, and shapes.
author Thinker K.F. Li <thinker@branda.to>
date Tue, 23 Sep 2008 09:09:34 +0800
parents 0de8fd11271e
children e96a584487af
comparison
equal deleted inserted replaced
140:0de8fd11271e 141:e89512d6fa0a
852 int n_areas, 852 int n_areas,
853 area_t **areas) { 853 area_t **areas) {
854 draw_coord_shapes_in_areas(rdman, rdman->root_coord, n_areas, areas); 854 draw_coord_shapes_in_areas(rdman, rdman->root_coord, n_areas, areas);
855 } 855 }
856 856
857
858 /*! \page coord_opacity How to support opacity attribute for group (coord)?
859 *
860 * I have several ideas to do that. This page show you all ideas.
861 *
862 * \section idea_one First One
863 * Change the structure of tree of coords. It is organized as tree of
864 * SVG document, shapes and coords are putten in tree with order the same
865 * as the document. The idea can solve the problem, but also seriously
866 * impact current code.
867 *
868 * \section idea_two Second One
869 * Add opacity and agg_opacity attribute to coord_t, and update
870 *
871 */
872 857
873 /*! \brief Re-draw all changed shapes or shapes affected by changed coords. 858 /*! \brief Re-draw all changed shapes or shapes affected by changed coords.
874 * 859 *
875 * A coord object has a geo to keep track the range that it's members will 860 * A coord object has a geo to keep track the range that it's members will
876 * draw on. Geo of a coord should be recomputed when the coord is changed. 861 * draw on. Geo of a coord should be recomputed when the coord is changed.