X-Git-Url: https://git.pterodactylus.net/?a=blobdiff_plain;ds=sidebyside;f=synfig-core%2Ftrunk%2Fsrc%2Fsynfig%2Fvaluenode_dynamiclist.h;h=e73afd97d31c07f51cc463d9a4879cf0e59d39bf;hb=bd7d31d7495dd11e060c2594ac5b62115e00b95c;hp=063cfbc55a78cbc043d2e53ddb682b0ce8c6862d;hpb=5ddcf36f04cfbd10fabda4e3c5633cb27cdd4c0a;p=synfig.git
diff --git a/synfig-core/trunk/src/synfig/valuenode_dynamiclist.h b/synfig-core/trunk/src/synfig/valuenode_dynamiclist.h
index 063cfbc..e73afd9 100644
--- a/synfig-core/trunk/src/synfig/valuenode_dynamiclist.h
+++ b/synfig-core/trunk/src/synfig/valuenode_dynamiclist.h
@@ -1,8 +1,8 @@
/* === S Y N F I G ========================================================= */
/*! \file valuenode_dynamiclist.h
-** \brief Template Header
+** \brief Header file for implementation of the "Dynamic List" valuenode conversion.
**
-** $Id: valuenode_dynamiclist.h,v 1.1.1.1 2005/01/04 01:23:15 darco Exp $
+** $Id$
**
** \legal
** Copyright (c) 2002-2005 Robert B. Quattlebaum Jr., Adrian Bentley
@@ -41,26 +41,27 @@
namespace synfig {
class ValueNode_BLine;
+class Canvas;
/*! \class ValueNode_DynamicList
** \brief Animated List ValueNode
**
-** This ValueNode was originaly set up to have a list
+** This ValueNode was originally set up to have a list
** of ValueNodes and their associated "on" and "off" points.
** ie: Any time that was directly after an "on" point,
** the item would be "on", and any time that was directly
** after an "off" point would be "off". This is pretty intuitive.
-** However, it does have it's problems.
+** However, it does have its problems.
**
-** The problems arrise when we introduce the concept of a
+** The problems arise when we introduce the concept of a
** Keyframe. Keyframes can be manipulated via the Synfig
** Application Library. They allow the user to quickly
-** and "automagickly" rearange an animation by moving
-** the associated keyframes. With they old way that the
+** and "automagically" rearrange an animation by moving
+** the associated keyframes. With the old way that the
** "on" and "off" points were handled, this task became
** overly complicated.
**
-** What is required is a "symetric" system of describing
+** What is required is a "symmetric" system of describing
** "on" and "off" points. Instead of the point representing
** the state of the item after that point in time, we have
** the point represent only that frame. The state
@@ -197,6 +198,8 @@ public:
bool get_loop()const { return loop_; }
void set_loop(bool x) { loop_=x; }
+ void set_member_canvas(etl::loose_handle