Initialise the priority when constructing a new Activepoint. Valgrind was complainin...
authordooglus <dooglus@1f10aa63-cdf2-0310-b900-c93c546f37ac>
Mon, 9 Apr 2007 19:32:22 +0000 (19:32 +0000)
committerdooglus <dooglus@1f10aa63-cdf2-0310-b900-c93c546f37ac>
Mon, 9 Apr 2007 19:32:22 +0000 (19:32 +0000)
git-svn-id: http://svn.voria.com/code@449 1f10aa63-cdf2-0310-b900-c93c546f37ac

synfig-core/trunk/src/synfig/activepoint.h

index be45c83..cdd7915 100644 (file)
@@ -1,3 +1,4 @@
+#include <stdio.h>
 /* === S Y N F I G ========================================================= */
 /*!    \file activepoint.h
 **     \brief Template Header
@@ -61,7 +62,8 @@ public:
        bool operator<(const Time& rhs) { return time<rhs; }
 
        Activepoint(const Time &time, const bool &state, int p=0): time(time), priority(p),state(state) { }
-       Activepoint() { }
+       //! \todo Should priority be initialised here, or elsewhere?  This avoids a valgrind warning for now.
+       Activepoint(): priority(0) { }
 
        const Time& get_time()const { return time; }
        void set_time(const Time& x) { time=x; }