<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://www.wiki.synfig.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=SvH</id>
		<title>Synfig Studio :: Documentation - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://www.wiki.synfig.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=SvH"/>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/Special:Contributions/SvH"/>
		<updated>2026-04-25T16:48:38Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.26.3</generator>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Releases/0.61.09&amp;diff=8486</id>
		<title>Releases/0.61.09</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Releases/0.61.09&amp;diff=8486"/>
				<updated>2009-02-24T16:10:14Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* ETL */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Released October 21 2008&lt;br /&gt;
&lt;br /&gt;
== ETL ==&lt;br /&gt;
&lt;br /&gt;
* Improved the derivative class for hermites (Spline curves).&lt;br /&gt;
&lt;br /&gt;
== Layers ==&lt;br /&gt;
&lt;br /&gt;
* Don't let feather be negative for any Shape layers or Circle layers.&lt;br /&gt;
* Fix handling of segments so that the examples/walk/walk.sifz file will load correctly.&lt;br /&gt;
* Use 0 for the index if the closest point is on the segment which closes the loop.  This keeps the final 'amount' value in the range 0..1.&lt;br /&gt;
* Fix a bug in the plant layer: when the plant is so small that we can't calculate the perpendicular to its bline, skip trying to branch it.&lt;br /&gt;
* Improve a warning message when we find an unknown layer parameter.&lt;br /&gt;
* Rename all 'pos' and 'offset' parameters to 'origin'.&lt;br /&gt;
* Add parameter 'add_width' to the [[Plant Layer|plant layer]].  It's on by default, and means to scale the velocity of a plant's shoot by the width of the bline at that point.&lt;br /&gt;
* Now circles with large feather and zero radius are visible.  Only shortcut zero-radius circles if they're not inverted and have no feathering. [http://sf.net/support/tracker.php?aid=2120629 2120629]&lt;br /&gt;
* Leave previously selected layers selected when creating a new one. Environment variable SYNFIG_TOOLS_CLEAR_SELECTION toggles this option.&lt;br /&gt;
* Add &amp;quot;select all layers&amp;quot; (S-C-a) and &amp;quot;unselect all ducks&amp;quot; (C-d).  Move &amp;quot;unselect all layers&amp;quot; onto S-C-d.&lt;br /&gt;
* When multiple layers are selected, only show parameters which are present in all selected layers *with the same type*.&lt;br /&gt;
&lt;br /&gt;
== Value Nodes ==&lt;br /&gt;
&lt;br /&gt;
*Add new types:&lt;br /&gt;
** [[Convert#Logarithm|Logarithm]]: To convert to a natural logarithm&lt;br /&gt;
** [[Convert#Int String|Int String]]: To convert to a string from an integer&lt;br /&gt;
** [[Convert#Angle String|Angle String]] : To convert to a string from an angle&lt;br /&gt;
** [[Convert#Joined List|Joined List]]: Join two strings&lt;br /&gt;
** [[Convert#Real String|Real String]]: To convert to a string from a real&lt;br /&gt;
** [[Convert#Time String|Time String]]: To convert to a string from a time&lt;br /&gt;
** [[Convert#Dot Product|Dot Product]]: Convert to a real from the dot product of two vectors&lt;br /&gt;
** [[Convert#Gradient Color|Gradient Color]]: Convert to a color from a gradient &lt;br /&gt;
** [[Convert#Vector X|Vector X]]: Convert to a real from a vector (get its X)&lt;br /&gt;
** [[Convert#Vector Y|Vector Y]]: Convert to a real from a vector (get its Y)&lt;br /&gt;
** [[Convert#Vector Length|Vector Length]]: Convert to a real from a vector (get its length)&lt;br /&gt;
** [[Convert#Vector Angle|Vector Angle]]: Convert to an angle from a vector (get its angle)&lt;br /&gt;
* Add &amp;quot;Loop&amp;quot; link to the &amp;quot;Gradient Color&amp;quot; ValueNode.&lt;br /&gt;
&lt;br /&gt;
== Targets ==&lt;br /&gt;
&lt;br /&gt;
* Unless OpenEXR half mode is used, don't ask synfigstudio to depend on it.&lt;br /&gt;
* Fix build problem with newer versions of libavformat due to the pb member of AVFormatContext changing from a structure to a pointer. [http://sf.net/support/tracker.php?aid=11877061 11877061]&lt;br /&gt;
* For mod_libav, allow the use of libswscale instead of the depreciated img_convert function [http://sf.net/support/tracker.php?aid=2036627 2036627], [http://bugs.debian.org/487639 487639]&lt;br /&gt;
* Fix the libjpeg configure test to look for the right function.&lt;br /&gt;
* Windows builds now include OpenEXR version 1.6.&lt;br /&gt;
* Configure now uses pkg-config to find libswscale. [http://sf.net/support/tracker.php?aid=2108984 2108984]&lt;br /&gt;
* Cope with some changes in the locations of the libavformat and libswscale headers.&lt;br /&gt;
* Add a configure flag to switch on/off jpeg support. Patch [http://patches.synfig.org/r/5/ 5]&lt;br /&gt;
&lt;br /&gt;
== Blend Methods ==&lt;br /&gt;
&lt;br /&gt;
* Fix this bug: when a layer was composed 'straight onto' a context with which its bounding box had no overlap, the context was being displayed as if the 'straight onto' layer wasn't there. [http://sf.net/support/tracker.php?aid=1960543 1960543]&lt;br /&gt;
&lt;br /&gt;
== Canvases ==&lt;br /&gt;
&lt;br /&gt;
* To allow backward compatibility, canvas version has been set to 0.6.&lt;br /&gt;
&lt;br /&gt;
== Files ==&lt;br /&gt;
&lt;br /&gt;
* In the 'open &amp;gt; recent files' menu entry, only show files which still exist.  Previously, it was saving documents into /tmp. After rebooting /tmp had been emptied, but the files were still showing up in the menu.&lt;br /&gt;
* Modified the Help menu due to the Communication page on the website being renamed to Contact.&lt;br /&gt;
* Fix error when trying to change value of Filename property. [http://sf.net/support/tracker.php?aid=1988939 1988939]&lt;br /&gt;
&lt;br /&gt;
== Settings ==&lt;br /&gt;
&lt;br /&gt;
* Added a new tab in the [[Setup Dialog|Setup Dialog]] to allow user set the preferences for: X and Y sizes for new documents, the new Document filename prefix and a selector for predefined resolutions.&lt;br /&gt;
&lt;br /&gt;
== Linking == &lt;br /&gt;
&lt;br /&gt;
Added new feature [[Linking to Blines| Link to Bline]]: allow the user link vertexes, tangents and widths to a parametrized position of a bline. Also inverse manipulation is allowed. This makes easier to build complex figures without need to have a vertex on the joining point.&lt;br /&gt;
&lt;br /&gt;
== Waypoints ==&lt;br /&gt;
&lt;br /&gt;
* [[TCB|TENSION and TEMPORAL TENSION]] were the same; use the 'temporal' version everywhere.&lt;br /&gt;
* Don't render waypoints that lie outside the bounds of the timetrack's adjustment. [http://sf.net/support/tracker.php?aid=1888863 1888863]&lt;br /&gt;
* Don't offer 'Manual' as an interpolation type.  It's not clear what it is supposed to do, and looks like the code to implement it was never written.  Attempting to use it causes uninitialized memory to be read.&lt;br /&gt;
&lt;br /&gt;
== Time ==&lt;br /&gt;
&lt;br /&gt;
*  Fix bad time entry when format is set to FFf. Patch [http://patches.synfig.org/r/4/ 4]&lt;br /&gt;
* Show time 3.0 as &amp;quot;3s&amp;quot; in the default (FORMAT_NORMAL) time display mode, rather than sometimes showing &amp;quot;3s 0f&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
== Windows ==&lt;br /&gt;
&lt;br /&gt;
=== Console Window ===&lt;br /&gt;
&lt;br /&gt;
* Make the file selector dialogs print less output to the console.&lt;br /&gt;
* Show the 'fifo_activity' message less.&lt;br /&gt;
* Show commands as they are received over the FIFO.&lt;br /&gt;
* Don't show debugging messages about saving preference directories.&lt;br /&gt;
&lt;br /&gt;
=== Toolbox Window ===&lt;br /&gt;
&lt;br /&gt;
* Add new icon for the reset colors button and change the code to use it.&lt;br /&gt;
The size of the foreground color and background color picker has been modified to allow the display of the reverse FG and BG colours and set FG and BG colors buttons properly in all GTK themes. Patch [http://patches.synfig.org/r/2/ 2]&lt;br /&gt;
&lt;br /&gt;
=== Workarea Window ===&lt;br /&gt;
&lt;br /&gt;
* Fix zoom fit so it really does zoom the canvas to fit the window. [http://sf.net/support/tracker.php?aid=1901244 1901244]&lt;br /&gt;
* Show a 'zoom to fit' icon in the zoomdial as well as a 'zoom 100%' icon.&lt;br /&gt;
* Fix &amp;quot;zoom to fit&amp;quot; so that it centers the fitted canvas on the screen, and always zooms back to the previous zoom level and position if clicked a second time.&lt;br /&gt;
&lt;br /&gt;
=== Canvas Properties Dialog ===&lt;br /&gt;
&lt;br /&gt;
* When calculating the start and end frames, round to the nearest integer rather than always rounding down.&lt;br /&gt;
* Editing the name, description, or id of a canvas should mark the canvas as needing to be saved, and should also be undoable. [http://sf.net/support/tracker.php?aid=1924592 1924592]&lt;br /&gt;
&lt;br /&gt;
=== Color Editor Dialog ===&lt;br /&gt;
&lt;br /&gt;
* Allow clicking or scrolling on color sliders to change the color.&lt;br /&gt;
&lt;br /&gt;
=== Gradient Editor Dialog ===&lt;br /&gt;
&lt;br /&gt;
* Properly manage the situation when all CPoints of a gradient are removed. [http://sf.net/support/tracker.php?aid=2096641 2096641]&lt;br /&gt;
&lt;br /&gt;
=== Time Track Panel ===&lt;br /&gt;
&lt;br /&gt;
* Update the timeline scrollbars' major step size when zooming time in and out. [http://sf.net/support/tracker.php?aid=1914874 1914874]&lt;br /&gt;
* Allow scrolling left and right in time widgets.&lt;br /&gt;
* Fix a bug that was causing the time slider to not be displayed in certain circumstances.&lt;br /&gt;
&lt;br /&gt;
=== Curves Panel ===&lt;br /&gt;
&lt;br /&gt;
* Don't show an incorrect error message when selecting a filename or canvas parameter.  The error message was due these types not being representable in the Curves panel, but this isn't an error. [http://sf.net/support/tracker.php?aid=2060732 2060732]&lt;br /&gt;
&lt;br /&gt;
=== Splash Screen ===&lt;br /&gt;
&lt;br /&gt;
* Use a new image by Yaco &amp;amp; Genete &lt;br /&gt;
&lt;br /&gt;
== Tools ==&lt;br /&gt;
&lt;br /&gt;
* Text, Plant, Polyline and Star have new icons.&lt;br /&gt;
* [[Circle Tool|Circle tool]] allows now make Blined circles too. Regions, Outlines, Gradients and Plants are included.&lt;br /&gt;
* [[ Rectangle Tool|Rectangle tool]] now does the same. &lt;br /&gt;
* New [[Text Tool| Text tool]] has been added to the [[Toolbox|ToolBox]]. &lt;br /&gt;
* New [[Star Tool|Star Tool]] has been added to the tool palette. It allows now make blined stars too. Regions, Outlines, Gradients and Plants are included.&lt;br /&gt;
* Now [[Eyedrop Tool|eyedropper]] works correctly with straight blends for following layers types: Region, Outline, Star, Polygon and Circle. Fix other layers is pending. [http://sf.net/support/tracker.php?aid=2119764 2119764]&lt;br /&gt;
* The &amp;quot;Link Offsets&amp;quot; option in the [[BLine Tool|BLine tool]] now only links offsets if we're creating more than one layer at a time.&lt;br /&gt;
* Added options to the circle tool for creation of bline approximations to circles. Number of points and points angle offset.&lt;br /&gt;
* Use the 'feather' and 'invert' tool options when creating outline or region layers in the circle tool.&lt;br /&gt;
* Remove the &amp;quot;blend method&amp;quot; option from the tool options panel for the circle and gradient tools (unless the BLEND_METHOD_IN_TOOL_OPTIONS #define in toolbox.h is uncommented).&lt;br /&gt;
* Add 'inner tangent', 'outer tangent' and 'radius ratio' options to the star tool for creating rounded stars and different ratios stars.&lt;br /&gt;
* Show the name of the current tool in the tool options panel if it has any options.  For the zoom tool, show the message that it doesn't have any options, instead of just showing a blank panel.&lt;br /&gt;
* Replace &amp;quot;Gradient&amp;quot; check button with &amp;quot;Create Gradient BLine&amp;quot;, etc., like in the other tools.&lt;br /&gt;
* Using the Circle tool over an existing duck now doesn't crash. [http://sf.net/support/tracker.php?aid=1959064 1959064]&lt;br /&gt;
* [[Width Tool]] is enabled now by default. And pretty usable.&lt;br /&gt;
&lt;br /&gt;
== Ducks ==&lt;br /&gt;
&lt;br /&gt;
* Fixed infinite error message loop on split tangents. [http://sf.net/support/tracker.php?aid=1947076 1947076]&lt;br /&gt;
&lt;br /&gt;
== Miscellaneous ==&lt;br /&gt;
&lt;br /&gt;
* Improve Segment Tangent and Bline Tangent calculations. Now they give more accurate results.&lt;br /&gt;
* If only one of -w and -h is specified on the command line, calculate the other in order to keep the aspect ratio fixed.&lt;br /&gt;
* Check for Gtk::AboutDialog::set_wrap_license, which was added in Gtkmm 2.8. Allows synfigstudio to build on the fink distribution.&lt;br /&gt;
* Update configure.ac as suggested by autoupdate.&lt;br /&gt;
* Improved GUI for the sound file selection dialog. [http://sf.net/support/tracker.php?aid=1932525 1932525]&lt;br /&gt;
* Alt-D = draw, Alt-W = width.  Previously there were 2 different definitions for Alt-T.&lt;br /&gt;
* More strings has been extracted to be marked as translatable. Spanish, French and Catalan translations Updated.&lt;br /&gt;
* Add multiple sizes and a scalable version of synfig_icon installed in freedesktop.org icon directories. [http://sf.net/support/tracker.php?aid=2109095 2109095]&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7197</id>
		<title>Roadmap</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7197"/>
				<updated>2008-05-30T15:32:18Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* 0.7 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
This page contains a roadmap with defined goals for each release. See [[Software roadmap]] for things we want to do with synfig at some point. See [[Release]] for the process we go through when releasing.&lt;br /&gt;
&lt;br /&gt;
As an open source project, synfig is relatively young. As a result, it has lots of creases that need to be ironed out. The copyright is sorted, the code compiles fine, but there are warts when running the code. To smooth out those warts, we need people do investigate and fix the following. We cannot do everything ourselves, WE NEED YOUR HELP!!&lt;br /&gt;
&lt;br /&gt;
== Tasks, to reach a final version of 1.0 ==&lt;br /&gt;
&lt;br /&gt;
=== 0.7 ===&lt;br /&gt;
* A different color dialog to easier pick and change colors.&lt;br /&gt;
** A color wheel like inkscape has (or the same)&lt;br /&gt;
** Swatch menu from gimp with .gpl files.&lt;br /&gt;
&lt;br /&gt;
=== 0.8 ===&lt;br /&gt;
* Workflow improvements, like content help and ui-refinement.&lt;br /&gt;
** set the fine line between design and animation work.&lt;br /&gt;
** Greet the user at startup, give hints and help in the ui to better the usability and user-experience.&lt;br /&gt;
* test synfig cross-platform (Linux, Windows, Mac)&lt;br /&gt;
* Installer for windows&lt;br /&gt;
* Pluggable App (run from memory stick)&lt;br /&gt;
* make a short film about synfigs capabilitys in a starwars kind of spaceship setting as promo video about 3 minutes long.&lt;br /&gt;
&lt;br /&gt;
=== 0.9 ===&lt;br /&gt;
* Sound layer&lt;br /&gt;
* full tablet support&lt;br /&gt;
* small set of vector contend for fast animation results&lt;br /&gt;
* Help is available as pdf-file and distributed with the program&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Input:'''&lt;br /&gt;
* Import rastergraphics png, jpg, tif [done]&lt;br /&gt;
* Import vectorgraphics (svg,fig)&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
* Render output to animated gif [done]&lt;br /&gt;
* Render output to png, bmp, OpenEXR [done] &lt;br /&gt;
* Export vectorgraphics (svg,fig)&lt;br /&gt;
&lt;br /&gt;
== Things, which are also accepted in our patch tracker==&lt;br /&gt;
&lt;br /&gt;
* create better builds for MacOS X.&lt;br /&gt;
* fixes for any of the open [[Bugs|bugs]].&lt;br /&gt;
* embedded source code documentation&lt;br /&gt;
* Write a tutorial&lt;br /&gt;
* translate into your language&lt;br /&gt;
* test synfig and confirm open bugs&lt;br /&gt;
&lt;br /&gt;
=== Easy coding tasks ===&lt;br /&gt;
Put here tasks for new developers, to make them able to dive into the code.&lt;br /&gt;
&lt;br /&gt;
* Synfigstudio needs verbosity levels for the error output. Levels are info, warning and error. Make sure, to spew out only errors when something nasty happens. If someone wants to know all what happens in synfigstudio, the user should activate a higher level of verbosity with the command line switch --verbose=all,info,warning&lt;br /&gt;
&lt;br /&gt;
* Synfig and Synfigstudio need a usage screen, which helps a new user to type in the right syntax on the command line. Any switch not known to the program should point to the usage screen. On the bottom of the usage screen could be a hint: &amp;quot; For more help use synfig --help&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==To the old [[Releases]]==&lt;br /&gt;
&lt;br /&gt;
Just for reference.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7196</id>
		<title>Roadmap</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7196"/>
				<updated>2008-05-30T14:59:36Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* 0.8 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
This page contains a roadmap with defined goals for each release. See [[Software roadmap]] for things we want to do with synfig at some point. See [[Release]] for the process we go through when releasing.&lt;br /&gt;
&lt;br /&gt;
As an open source project, synfig is relatively young. As a result, it has lots of creases that need to be ironed out. The copyright is sorted, the code compiles fine, but there are warts when running the code. To smooth out those warts, we need people do investigate and fix the following. We cannot do everything ourselves, WE NEED YOUR HELP!!&lt;br /&gt;
&lt;br /&gt;
== Tasks, to reach a final version of 1.0 ==&lt;br /&gt;
&lt;br /&gt;
=== 0.7 ===&lt;br /&gt;
* Synfigstudio needs a man page&lt;br /&gt;
&lt;br /&gt;
=== 0.8 ===&lt;br /&gt;
* Workflow improvements, like content help and ui-refinement.&lt;br /&gt;
** set the fine line between design and animation work.&lt;br /&gt;
** Greet the user at startup, give hints and help in the ui to better the usability and user-experience.&lt;br /&gt;
* test synfig cross-platform (Linux, Windows, Mac)&lt;br /&gt;
* Installer for windows&lt;br /&gt;
* Pluggable App (run from memory stick)&lt;br /&gt;
* make a short film about synfigs capabilitys in a starwars kind of spaceship setting as promo video about 3 minutes long.&lt;br /&gt;
&lt;br /&gt;
=== 0.9 ===&lt;br /&gt;
* Sound layer&lt;br /&gt;
* full tablet support&lt;br /&gt;
* small set of vector contend for fast animation results&lt;br /&gt;
* Help is available as pdf-file and distributed with the program&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Input:'''&lt;br /&gt;
* Import rastergraphics png, jpg, tif [done]&lt;br /&gt;
* Import vectorgraphics (svg,fig)&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
* Render output to animated gif [done]&lt;br /&gt;
* Render output to png, bmp, OpenEXR [done] &lt;br /&gt;
* Export vectorgraphics (svg,fig)&lt;br /&gt;
&lt;br /&gt;
== Things, which are also accepted in our patch tracker==&lt;br /&gt;
&lt;br /&gt;
* create better builds for MacOS X.&lt;br /&gt;
* fixes for any of the open [[Bugs|bugs]].&lt;br /&gt;
* embedded source code documentation&lt;br /&gt;
* Write a tutorial&lt;br /&gt;
* translate into your language&lt;br /&gt;
* test synfig and confirm open bugs&lt;br /&gt;
&lt;br /&gt;
=== Easy coding tasks ===&lt;br /&gt;
Put here tasks for new developers, to make them able to dive into the code.&lt;br /&gt;
&lt;br /&gt;
* Synfigstudio needs verbosity levels for the error output. Levels are info, warning and error. Make sure, to spew out only errors when something nasty happens. If someone wants to know all what happens in synfigstudio, the user should activate a higher level of verbosity with the command line switch --verbose=all,info,warning&lt;br /&gt;
&lt;br /&gt;
* Synfig and Synfigstudio need a usage screen, which helps a new user to type in the right syntax on the command line. Any switch not known to the program should point to the usage screen. On the bottom of the usage screen could be a hint: &amp;quot; For more help use synfig --help&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==To the old [[Releases]]==&lt;br /&gt;
&lt;br /&gt;
Just for reference.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7195</id>
		<title>Roadmap</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7195"/>
				<updated>2008-05-30T13:49:37Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* 0.9 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
This page contains a roadmap with defined goals for each release. See [[Software roadmap]] for things we want to do with synfig at some point. See [[Release]] for the process we go through when releasing.&lt;br /&gt;
&lt;br /&gt;
As an open source project, synfig is relatively young. As a result, it has lots of creases that need to be ironed out. The copyright is sorted, the code compiles fine, but there are warts when running the code. To smooth out those warts, we need people do investigate and fix the following. We cannot do everything ourselves, WE NEED YOUR HELP!!&lt;br /&gt;
&lt;br /&gt;
== Tasks, to reach a final version of 1.0 ==&lt;br /&gt;
&lt;br /&gt;
=== 0.7 ===&lt;br /&gt;
* Synfigstudio needs a man page&lt;br /&gt;
&lt;br /&gt;
=== 0.8 ===&lt;br /&gt;
&lt;br /&gt;
=== 0.9 ===&lt;br /&gt;
* Sound layer&lt;br /&gt;
* full tablet support&lt;br /&gt;
* small set of vector contend for fast animation results&lt;br /&gt;
* Help is available as pdf-file and distributed with the program&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Input:'''&lt;br /&gt;
* Import rastergraphics png, jpg, tif [done]&lt;br /&gt;
* Import vectorgraphics (svg,fig)&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
* Render output to animated gif [done]&lt;br /&gt;
* Render output to png, bmp, OpenEXR [done] &lt;br /&gt;
* Export vectorgraphics (svg,fig)&lt;br /&gt;
&lt;br /&gt;
== Things, which are also accepted in our patch tracker==&lt;br /&gt;
&lt;br /&gt;
* create better builds for MacOS X.&lt;br /&gt;
* fixes for any of the open [[Bugs|bugs]].&lt;br /&gt;
* embedded source code documentation&lt;br /&gt;
* Write a tutorial&lt;br /&gt;
* translate into your language&lt;br /&gt;
* test synfig and confirm open bugs&lt;br /&gt;
&lt;br /&gt;
=== Easy coding tasks ===&lt;br /&gt;
Put here tasks for new developers, to make them able to dive into the code.&lt;br /&gt;
&lt;br /&gt;
* Synfigstudio needs verbosity levels for the error output. Levels are info, warning and error. Make sure, to spew out only errors when something nasty happens. If someone wants to know all what happens in synfigstudio, the user should activate a higher level of verbosity with the command line switch --verbose=all,info,warning&lt;br /&gt;
&lt;br /&gt;
* Synfig and Synfigstudio need a usage screen, which helps a new user to type in the right syntax on the command line. Any switch not known to the program should point to the usage screen. On the bottom of the usage screen could be a hint: &amp;quot; For more help use synfig --help&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==To the old [[Releases]]==&lt;br /&gt;
&lt;br /&gt;
Just for reference.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Dev:Wish_list&amp;diff=7194</id>
		<title>Dev:Wish list</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Dev:Wish_list&amp;diff=7194"/>
				<updated>2008-05-30T09:32:28Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Smartrendering */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''''Warning''''': We need more people working on the code if we are going to be able to achieve all the feature requests.&lt;br /&gt;
&lt;br /&gt;
Got a great idea for a new feature? Just add it here, or on the [http://sourceforge.net/tracker/?group_id=144022&amp;amp;atid=757419 feature requests tracker]. Before you do, please check the [http://svn.voria.com/code/ETL/trunk/TODO etl], [http://svn.voria.com/code/synfig-core/trunk/TODO synfig] and [http://svn.voria.com/code/synfig-studio/trunk/TODO synfigstudio] TODO files for similar ideas. Please add a rating of how essential this feature is to your workflow according to the following scale:&lt;br /&gt;
&lt;br /&gt;
#&amp;quot;Well, it might be nifty. To someone.&amp;quot;&lt;br /&gt;
#&amp;quot;I probably would make use this&amp;quot;&lt;br /&gt;
#&amp;quot;It's not essential, but I'd really like to have this at my disposal.&amp;quot;&lt;br /&gt;
#&amp;quot;Synfig would be soooo much better with this change&amp;quot;&lt;br /&gt;
#&amp;quot;I can't/won't use Synfig without it!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== Wishes ==&lt;br /&gt;
&lt;br /&gt;
===Movement blur effect===&lt;br /&gt;
To make the motion most realistic for movies, it should be possible to activate in the render dialog the option to smear the border of all objects, which move faster than a given value. For example, if a ball gets shot over the canvas/rendering-screen with speed over 50 px/frame it should have a blurry streak attached. This effect could be applied only at rendering time as an after-effect. --[[User:SvH|SvH]] 09:50, 28 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
:There is a [[Motion Blur Layer]] that you can apply to the entire document or to the layers you want. It allows to turn the blur effect on and off during animation. I think it is more flexible that your proposal. [[User:Genete|Genete]] 10:13, 28 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
===Morph sets===&lt;br /&gt;
This feature is similar to some other suggestions below, just with another way to approach. In animations are many movements, which can be put in some kind of library, to make use of at a later time. For example, movements to animate the key moments of a mouth, sampling syllables. For vector graphics, it should be possible to define some key points, which move just a small amount of space, to form another syllable. These syllables in this example, should be stored in a drop down list, to be able to select them for the key time on the timeline.&lt;br /&gt;
A morph-set for walking-left-to-right is different from a morph-set for a mounth, which has as options a,e,i,o,u,bah-disgust,happy-smile. The morph-set has to be stored as vector coordinates in a relative way(offset), e.g. X1=+212,+34;X2=-56,-23;X3=+3,-88;&lt;br /&gt;
&lt;br /&gt;
To make use of the morph-set for the mouth, you have to define first, which vector points in your drawn mouth, correspond to the key-points of your morph-set. X1, X2, X3, Xn&lt;br /&gt;
&lt;br /&gt;
--[[User:SvH|SvH]] 06:53, 27 May 2008 (EDT)&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
===Render time approximation===&lt;br /&gt;
Synfigstudio should get a button in the render dialog, which calculates the total render time for the actual settings (frames per second, length of the film, resolution, output format) It should testrender 1 picture, when the amount of total frames is below 1000. Over 1000 frames, it should testrender 10 pictures for more precise calculation.&lt;br /&gt;
&lt;br /&gt;
--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
===Smartrendering===&lt;br /&gt;
I have made 25,000 small png-pictures with my 800Mhz computer in about 45 minutes. Synfigstudio did calculate each single frame of it. Nothing changed in this picture, so it does only need to get written to disk for the amount of pictures, until the next change (animation) has an effect on the output picture. This should save time for bigger projects with thousands of pictures. With smartrendering it is also possible to predict the total amound of space in Megabytes (Mibibytes) of the final render of the movie. It should calculate how much it needs and see, if enough space is free on the harddisk before the rendering get started.&lt;br /&gt;
&lt;br /&gt;
--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== get_color method in text and radial blur ===&lt;br /&gt;
&lt;br /&gt;
[5] Without get_color method distorion produces artifacts &lt;br /&gt;
[http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1831355&amp;amp;group_id=144022&amp;amp;atid=757416 bug  1831355]. So I would like to get this problem fixed before doing something else. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== Full functional of group dialog ===&lt;br /&gt;
&lt;br /&gt;
[5] Group dialog is broken now [http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1796833&amp;amp;group_id=144022&amp;amp;atid=757416 bug 1796833]. So we should get old features work right before making new one. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== import/export .swf files ===&lt;br /&gt;
&lt;br /&gt;
very important productivity feature&lt;br /&gt;
&lt;br /&gt;
=== import/export .svg frames sequence, and/or .svg animations ===&lt;br /&gt;
&lt;br /&gt;
very important productivity feature&lt;br /&gt;
&lt;br /&gt;
=== a realtime .sif synchronized text window ===&lt;br /&gt;
&lt;br /&gt;
just like the xml editor of Inkscape, or the html editor in Dreamweaver (this is hugelly useful for productivity)&lt;br /&gt;
&lt;br /&gt;
I thinks scripting API can be implement in this way. For example you make XML DOM like implementation for python which alows to change DOM tree from python code and see chenges in canvas. By this way you can implement import/export scripts. Automation scripts. And a lot of different things. Even synchronization of animation between blender and synfig. --[[User:AkhIL|AkhIL]] 23:10, 26 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== choosing colour from gimp/inkscape palettes ===&lt;br /&gt;
&lt;br /&gt;
very useful when you need some colour comformity of what you're doing &lt;br /&gt;
&lt;br /&gt;
=== Good high-level documentation of the source code ===&lt;br /&gt;
&lt;br /&gt;
(2) It'd be nice if a newbie could quickly navigate around the source code. The best thing to do would be to add top-level comments in each file, explaining what that file does, a README.TXT in each directory, explaining what's in that directory. This would be pretty fast and easy to do, and make it much easier for new programmers to join. &lt;br /&gt;
&lt;br /&gt;
Time permitting, it would also be good to document on a high level what the data structures are, but that's harder, since those tend to evolve, and it is often difficult to keep in sync. It would also be useful to document what individual functions do (just a one-liner high-level description), but that also takes more time.&lt;br /&gt;
: There is a page link in the wiki that connect to the [http://www.synfig.com/doc Synfig API Documentation]. I think this link should be highlighted to be more accessible for newbies contributors and mature developers (the link was found [[Releases/DeveloperPreview#Support | here]]). --[[User:Genete|Genete]] 10:02, 11 December 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Mathematical functions to animate ===&lt;br /&gt;
(2/4) If you want to make a waving flag, it would be handful a sine function, tuned with random correctors, for example. &lt;br /&gt;
: -This should generate waypoints each 1, 2, 4 frames or any other step at artist's wish.&lt;br /&gt;
: -When applying a function you can add it to current values, add it to 1st frame values or simply override old values. Perhaps other options (such multiplication) would be fine, too. Something like texture editor in [http://www.artofillusion.org Art of Illusion], perhaps.&lt;br /&gt;
Perhaps it would be useful reusing the [http://www.gnu.org/software/octave/ Octave] source code to parse mathematical expressions.&lt;br /&gt;
I have rated this wish with a '2' because undoubtly many users will not be familiar to mathematical concepts, but for those who will be, I'd rate it with a 4. It would be possible to make a ball describing a parabolic moving in no time.&lt;br /&gt;
[[User:ajotatxe|ajotatxe]] 20 November 2007&lt;br /&gt;
: dooglus can probably chime in better than I here (see his example of balls on mathematical paths at http://uk.youtube.com/watch?v=YTpSfUthuVE ), but I believe that this is already possible.  Synfig does support a variety of mathematical transforms for parameters, although the way you do this is by no means intuitive.  (You might also want to check out the preambletaffy.sifz example for an easier approach to a waving flag. I know you were just using that as an example, but for the record...) [[User:Pxegeek|Pxegeek]] 00:58, 21 November 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
: I'd also rate it with a (4) (and updated the rating accordingly), not for this special case, but to make many workarounds much easier.  Simulating [Parabolic Shot|free fall], for example, would be a lot easier with real formulas.  I don't know, though how easy it will be to implement, maybe waiting for a scripting interface to be implemented is better than hacking this feature in an ad-hoc manner.  --[[User:Rubikcube|Rubikcube]] 16:38, 29 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Warning about editing bizarre things in animate editing mode ===&lt;br /&gt;
(3.5) It seems to have little sense animate certain things like Blend Method or Type of Feather. It would be very nice that the program asked comfirmation if you change these attributes in animate editing mode. If you do want to, you would have three options: &amp;quot;Yes, never ask&amp;quot;, &amp;quot;Yes, never ask for this attribute&amp;quot;, &amp;quot;No&amp;quot;. I guess that internally, this attributes has integer type (or something like that) and the attributes that you normally want to animate, float type, so I think that this feature is relatively easy to implement. My English is not very good, so please feel free to fix this post.&lt;br /&gt;
[[User:ajotatxe|ajotatxe]] 20 November 2007&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bones with FK &amp;amp; IK + grouping of objects into folders ===&lt;br /&gt;
&lt;br /&gt;
(1) Bones cane move specific vector assigned to them or the bones can have envelopes that move the vectors within their field of influence, much Like Anime Studio/Moho does. It's quite a time saving process of animating. Objects created can be saved into separate groups or folders using the same system as Anime Studio/Moho -Shadowphoenix 27/8/2007&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Animated sketch ===&lt;br /&gt;
&lt;br /&gt;
(1) it would be great, if the tool Sketch was animatable (for example, in a form of a special sketch-layer). --Zelgadis 2007-06-14&lt;br /&gt;
&lt;br /&gt;
=== Duck for Amount value in Zoom layer ===&lt;br /&gt;
&lt;br /&gt;
(2) It would be nice if Amount value in Zoom layer was controlled by additional duck. --[[User:Zelgadis|Zelgadis]] 02:49, 29 December 2007 (EST)&lt;br /&gt;
: I found that I can better use Warp layer instead of Zoom to change size. But it'd be nice to have Amount duck for Zoom layer anyway...&lt;br /&gt;
:: The Amount parameter works exponentially; each time you add 1 to the Amount, the image is zoomed by a further factor of e (= 2.71828 or so).  Would a duck be any use if it just controlled the value of Amount in a linear way?&lt;br /&gt;
:: Workarounds include: export Amount, select it in the children dialog.  Whatever's selected in the children dialog shows a duck.  You can adjust it using that duck.&lt;br /&gt;
:: Also, if you use a Stretch layer, convert the Amount to Composite, export the X-Axis and connect it to the Y-Axis, then you have a duck-controllable fixed-aspect zoom. -- [[User:Dooglus|dooglus]] 15:32, 15 January 2008 (EST)&lt;br /&gt;
::: Yeah I found this workaround, but it's to much actions - i prefer better use Warp or Stretch layers. Why not the link Amount duck and Amount value with logarithmic function? ;) --[[User:Zelgadis|Zelgadis]] 10:33, 17 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatic colour palette optimisation ===&lt;br /&gt;
&lt;br /&gt;
(0) it would be nice to use libcontrast [http://david.navi.cx/blog/?p=132] [http://david.navi.cx/blog/?p=94] [http://david.navi.cx/blog/?p=99] [http://svn.gnome.org/svn/xchat-gnome/trunk/src/libcontrast/] to automatically adjust selected or all the palette items for best visual contrast. It would also be interesting to have a layer that uses this code to filter the image.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arbitrary Color Channels ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; The ability for the user to create any number of custom channels for various purposes.&lt;br /&gt;
&lt;br /&gt;
=== Autorecover History ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; It would be great if autorecover could also recover the associated history of a file in the event of a crash.&lt;br /&gt;
&lt;br /&gt;
=== Layer Convert ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;(4)&amp;lt;/strike&amp;gt; (2) &amp;amp;mdash; The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''&lt;br /&gt;
&lt;br /&gt;
=== Vector fill bucket ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[Region Layer|region layer]]). &amp;lt;p&amp;gt;Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;If this is implemented, it will probably be necessary to change the existing &amp;quot;fill&amp;quot; tool's name and icon to a &amp;quot;color injector&amp;quot; (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.&lt;br /&gt;
&lt;br /&gt;
*Inkscape has a very innvative version of this tool. Maybe you can just grab the code from there and integrate it in synfig? --[[User:SvH|SvH]] 01:37, 14 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== [[redraw tool]] ===&lt;br /&gt;
&lt;br /&gt;
(4-5) &amp;amp;mdash; Intutive reshaping of path-based layers. See link.&lt;br /&gt;
&lt;br /&gt;
=== [http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance] ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; This should solve all complaints about the layout, without requiring Synfig to be &amp;quot;just like program (x)&amp;quot;. See [[UI Reloaded]] for progress on this.&lt;br /&gt;
&lt;br /&gt;
=== Feedback for [[Smooth Move Tool]] ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; This tool does what a lot of folks are looking for, warping selected ducks in a &amp;quot;soft&amp;quot; fashion. But it's not very obvious what sort of effect it will have, from the tool's interface. It needs some sort of momentary center-of-action and radius indicator at the very least. Perhaps an &amp;quot;influence gradient&amp;quot; overlaid on the canvas once Synfig's core is sped up?&lt;br /&gt;
&lt;br /&gt;
=== Networkability ===&lt;br /&gt;
&lt;br /&gt;
(2) &amp;amp;mdash; Like Inkscape's &amp;quot;inkboard&amp;quot; feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option. This should probably farm off all the networking stuff to the telepathy framework so that synfig doesn't have to deal with all the account/etc issues.&lt;br /&gt;
&lt;br /&gt;
=== Intuitive tangent modification ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.&lt;br /&gt;
&lt;br /&gt;
-Agreed; blender does this with its IPO curves, and it's a really efficient way to work.&lt;br /&gt;
&lt;br /&gt;
=== Plugin API ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
=== Python support ===&lt;br /&gt;
&lt;br /&gt;
(1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.&lt;br /&gt;
&lt;br /&gt;
I suuose to join this request with [[Wish_list#a_realtime_.sif_synchronized_text_window]]. We can implement python access to XML DOM and write XML Editor in python. --[[User:AkhIL|AkhIL]] 06:54, 30 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== mod_synfig ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; For Apache. Render .sif to some format like png/mng on access.&lt;br /&gt;
&lt;br /&gt;
=== synfig nsplugin ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; Let Mozilla and Mozilla-based view synfig files in-browser.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Align function ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; Align objects at a common border (as in Inkscape)&lt;br /&gt;
&lt;br /&gt;
=== Improved SVG import ===&lt;br /&gt;
&lt;br /&gt;
(4) &amp;amp;mdash; Currently, all importing an SVG does is render it in ImageMagick. What I want is the ability to import the SVG document so that all the shapes, etc. of the SVG document show up as their equivilant synfig layers - i.e. if I had put them there myself. I'm trying to write a patch for this but the codebase is mostly undocumented. [[User:KMeist|KMeist]] 16:38, 25 Feb 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
[[svg2synfig]] could be incorporated using an open source XSLT processor. --[[User:Dmd|Dmd]] 13:34, 26 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Gradient Paint Tool ===&lt;br /&gt;
&lt;br /&gt;
How about a tool that can 'paint' a gradient object.  For example the options would be width and gradient type, one would make a stroke with the tool and the gradient would be automatically applied inside of the outline (set by width).  This would save the trouble of having to the all the encapsulation stuff. (Actually any tool that makes creating gradient one step would be good).--[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bone Animation Tools ===&lt;br /&gt;
&lt;br /&gt;
Bone system with inverse kinematics, very important for quick animation. You put bones on a drawed man and you can animate him like a puppet. I'm using that in Moho (lost marble product).--[[User:Ziolive|ziolive]] 23 Aug 2006&lt;br /&gt;
*I would find this very useful too. I think it is called '''rigging'''(4/5) --[[User:SvH|SvH]] 01:33, 14 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== AVI Backgrounds ===&lt;br /&gt;
Is there any way I can add an avi as a background so I could add facial expressions to a stop-motion animated figure. [zotz here, I was thinking DV background or extra timeline. I would like to mix animations with live footage. rating (3/4)]&lt;br /&gt;
&lt;br /&gt;
=== Character tool on Tool Options Dialog ===&lt;br /&gt;
&lt;br /&gt;
I want to use the as a character generator for a TV show. By using chroma key hide the background.  Even better interface to a video overlay card with Alpha blending.&lt;br /&gt;
&lt;br /&gt;
=== Collect for Publication ===&lt;br /&gt;
&lt;br /&gt;
(3/4) - (zotz) Menu item, functionality that would collect alll files referenced in a sif and place them all in a tgz for sending elsewhere or publishing anumations in source form.&lt;br /&gt;
&lt;br /&gt;
=== Object Library ===&lt;br /&gt;
&lt;br /&gt;
(3/4) - (zotz) Haven't thought this all through yet, but synfig could come with a library of categotrised &amp;quot;objects&amp;quot; with a copyleft license (GPL?  CC BY-SA?) An animation clip art type deal.&lt;br /&gt;
**I'd suggest this should be public domain and distributed by openclipart.org -- --[[User:PaulWise|pabs]]&lt;br /&gt;
&lt;br /&gt;
=== Flash Export ===&lt;br /&gt;
&lt;br /&gt;
(3/4) Well, might just be me but if there was a posiblity to  export in .swf or .fla, I think the project might become a lot more popular.[[User:Conceit|Conceit]]&lt;br /&gt;
&lt;br /&gt;
(4/5) I wholeheartedly agree. I would definitely use synfig more if this feature were added and it would most definitely increase popularity. [[User:cdj05a|cdj05a]]&lt;br /&gt;
&lt;br /&gt;
=== Single window ===&lt;br /&gt;
&lt;br /&gt;
Depending on individual desktop setups, single window is sometimes preferable to many  windows. Can we have a single-window option?&lt;br /&gt;
&lt;br /&gt;
Also, even with many windows, Windows-users especially might find it better if all the windows only appeared as a single one on the taskbar.&lt;br /&gt;
&lt;br /&gt;
=== Line width tool ===&lt;br /&gt;
(4) It will be good to have a tool for easy changing line width. There was a such tool in earlier versions, but it's not usable. I'm often use variable line width, when drawing in synfig, so it is important for me. -- [[User:Zelgadis|Zelgadis]] 2007-09-09&lt;br /&gt;
&lt;br /&gt;
: It is [[FAQ#Where did the polygon, draw, sketch, and width tools go?|still available]].  Also, you can turn on the width ducks, using Alt-5. -- [[User:Dooglus|dooglus]] 12:18, 9 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
:: It is available, but I never was able to figure out how it works. Alt-5 works, but it is hard to set width to zero, for example. -- [[User:Zelgadis|Zelgadis]] 2007-09-10&lt;br /&gt;
&lt;br /&gt;
::: Are you wanting something that works on one vertex at a time?  Or all the vertices in an area?  Apparently the width tool was designed to work on a bunch of vertices at once.  I didn't figure out how it works though, either. -- [[User:Dooglus|dooglus]] 16:57, 10 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
:::: Width tool is surely a mystery. :) I'm waiting for something that works on one vertex at time. I liked the way as width was changed in Moho (Anime Studio now) - there was a special width tool and holding left mouse button on the vertex and moving cursor left decreasing width value, moving right - increasing. Maybe it make sense to rework Width tool in such way. -- [[User:Zelgadis|Zelgadis]] 2007-09-13&lt;br /&gt;
&lt;br /&gt;
::In my opinion the use of a seperate device like a joystick could help. You draw the line with the mouse and with the other hand, you push/pull the joystick to change the linewith in realtime. --[[User:SvH|SvH]] 05:25, 30 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== Export Wizard ===&lt;br /&gt;
&lt;br /&gt;
(2/4) Conversion and export to other file formats (mpg, avi, flash formats, others, and the synfig format) with a step by step wizard for choosing format and place of saving. Similar to Gimp's saving of .png files but for movie/video type files. --&lt;br /&gt;
[[User:Hiddenghost|hiddenghost]]&lt;br /&gt;
&lt;br /&gt;
=== Using Synfig as a portable app ===&lt;br /&gt;
&lt;br /&gt;
(3) This isn't really a feature request (though it could be) but I was wondering if synfig could be used as a portable application (as in www.portableapps.com). Does the windows install require registry access? i really want to use Synfig at work, but I'm reluctant to install it just in case it leave footprints in the regisitry or something, and it would be sweet to use it on my travels as well. Only thing is, I can't test it out at home because I am using Linux.&lt;br /&gt;
See also: http://portableapps.com/node/5761&lt;br /&gt;
[[User:Zenoscope|zenoscope]]&lt;br /&gt;
&lt;br /&gt;
This isn't currently possible without modifying the source code. That has been on my TODO list for ages [[User:PaulWise|pabs]] 01:17, 26 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Allow organize child valuenodes in an hierarchy ===&lt;br /&gt;
(3-2) And allow maintain the organization once the file is saved. At the moment they are reordered in alphabetical order which is useless and annoying.&lt;br /&gt;
&lt;br /&gt;
=== Triangle sliders to be always visible ===&lt;br /&gt;
(3) I would like that the triangle sliders from [[Colors Dialog]] and [[Gradient Editor Dialog]] were visible whatever color or channel you're editing. Some times when the color or channel is to bright or light the slider is difficult to distinguish. --[[User:Genete|Genete]] 14:30, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== XICC support ===&lt;br /&gt;
&lt;br /&gt;
It would be cool if synfigstudio had support for [http://burtonini.com/blog/computers/xicc XICC].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Area to Edit ===&lt;br /&gt;
&lt;br /&gt;
An option like blender - select area to update would be nice, so the only part of the image that updates when you add or change something is in the selected area&lt;br /&gt;
&lt;br /&gt;
ie. when working on a complex composition, studio doesn't know, when I tweak a tiny part of the composition, that only that part needs redrawing, so it redraws the whole thing.  It would be good if there was some way of telling it which part to focus on. -- [[User:Dooglus|dooglus]] 04:02, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Histograms ===&lt;br /&gt;
&lt;br /&gt;
 01:23  * AkhIL wish to have histograms and luma/color scope like [http://mac.softpedia.com/progScreenshots/Avid-Xpress-DV-Screenshot-14207.html] in synfig&lt;br /&gt;
&lt;br /&gt;
I've looked at those pictures but don't know what they're showing.  Can you describe what those scopes are doing, and what the histograms display?  ie. what are the X and Y axes of the histograms? -- [[User:Dooglus|dooglus]] 04:07, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
First look this description in blender wiki [http://wiki.blender.org/index.php/Manual/VSE_Modes]&lt;br /&gt;
&lt;br /&gt;
Ok There is four things.&lt;br /&gt;
* Upper left is Lumascope (Luma Waveform in blender). X-Axis represents image's X-Axys. Y-Axis  is average luminescence of column of pixels.&lt;br /&gt;
* Upper right is Chromascope (Chroma Vectorscope in blender). Just look description on blender wiki.&lt;br /&gt;
* Lower left is like Lumascope but for each channel &lt;br /&gt;
* Lower right is histograms. X is luminescence and Y is count of pixels with such luminiscence.&lt;br /&gt;
&lt;br /&gt;
=== Sound Layer ===&lt;br /&gt;
&lt;br /&gt;
(4) It would be a very good improvement if the sound system were implemented into synfig in [[Sound Layer | this]] way. --[[User:Genete|Genete]] 07:46, 8 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Rearrange the view of waypoints for Canvas param ===&lt;br /&gt;
As reported in [http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1888858&amp;amp;group_id=144022&amp;amp;atid=757416 Bug #1888858] waypoints are not displayed for canvas switch events.&lt;br /&gt;
I suggest to rearrange waypoints display according to [[Media:Canvas_prop.png|this scheme]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Width weigths ===&lt;br /&gt;
Is it possible to add &amp;quot;weigths&amp;quot; for widths? ^_^ I.e. width changes not all the way along the segment. Maybe something like a duck on bline which indicates the region where the width of current vertex isn't changed.&lt;br /&gt;
[[Media:width-proposal.png|Illustration here.]]&lt;br /&gt;
&lt;br /&gt;
More ideas around this concept in [http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-04-16.log this conversation]. Although the log of that day is very interesting the lines related to this idea are from 22:38 to 23:43. [[User:Genete|Genete]] 17:51, 16 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Improved Colour Dialog ===&lt;br /&gt;
How easy is it to stick in a colour square/wheel? Messing with sliders is somewhat obstructive.&lt;br /&gt;
&lt;br /&gt;
=== Insert Waypoints ===&lt;br /&gt;
A button to create a waypoint for every selected duck, in its current position. Moving each duck up a bit and down again quickly gets tedious.&lt;br /&gt;
:If the duck in question has already a waypoint then you don't need to move it to create a new waypoint. Just select the corresponding parameter in your child list panel and select 'Add Waypoint' from the right click context menu over the parameter. No need to have the duck selected. If you want to freeze the entire bline just do that over the Bline Point List. [[User:Genete|Genete]] 07:48, 29 April 2008 (EDT)&lt;br /&gt;
::Yes, but it would be nice to have opportunity to add waypoint to parameer which not have any ducks yet (i.e. non-animated parameter). --[[User:Zelgadis|Zelgadis]] 08:33, 29 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatically split tangeants ===&lt;br /&gt;
&lt;br /&gt;
Holding shift while moving tangeant ducks should automatically split them. They can be rejoined if necessary through the context menu as they are now.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Dev:Wish_list&amp;diff=7193</id>
		<title>Dev:Wish list</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Dev:Wish_list&amp;diff=7193"/>
				<updated>2008-05-30T09:25:37Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Line width tool */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''''Warning''''': We need more people working on the code if we are going to be able to achieve all the feature requests.&lt;br /&gt;
&lt;br /&gt;
Got a great idea for a new feature? Just add it here, or on the [http://sourceforge.net/tracker/?group_id=144022&amp;amp;atid=757419 feature requests tracker]. Before you do, please check the [http://svn.voria.com/code/ETL/trunk/TODO etl], [http://svn.voria.com/code/synfig-core/trunk/TODO synfig] and [http://svn.voria.com/code/synfig-studio/trunk/TODO synfigstudio] TODO files for similar ideas. Please add a rating of how essential this feature is to your workflow according to the following scale:&lt;br /&gt;
&lt;br /&gt;
#&amp;quot;Well, it might be nifty. To someone.&amp;quot;&lt;br /&gt;
#&amp;quot;I probably would make use this&amp;quot;&lt;br /&gt;
#&amp;quot;It's not essential, but I'd really like to have this at my disposal.&amp;quot;&lt;br /&gt;
#&amp;quot;Synfig would be soooo much better with this change&amp;quot;&lt;br /&gt;
#&amp;quot;I can't/won't use Synfig without it!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== Wishes ==&lt;br /&gt;
&lt;br /&gt;
===Movement blur effect===&lt;br /&gt;
To make the motion most realistic for movies, it should be possible to activate in the render dialog the option to smear the border of all objects, which move faster than a given value. For example, if a ball gets shot over the canvas/rendering-screen with speed over 50 px/frame it should have a blurry streak attached. This effect could be applied only at rendering time as an after-effect. --[[User:SvH|SvH]] 09:50, 28 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
:There is a [[Motion Blur Layer]] that you can apply to the entire document or to the layers you want. It allows to turn the blur effect on and off during animation. I think it is more flexible that your proposal. [[User:Genete|Genete]] 10:13, 28 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
===Morph sets===&lt;br /&gt;
This feature is similar to some other suggestions below, just with another way to approach. In animations are many movements, which can be put in some kind of library, to make use of at a later time. For example, movements to animate the key moments of a mouth, sampling syllables. For vector graphics, it should be possible to define some key points, which move just a small amount of space, to form another syllable. These syllables in this example, should be stored in a drop down list, to be able to select them for the key time on the timeline.&lt;br /&gt;
A morph-set for walking-left-to-right is different from a morph-set for a mounth, which has as options a,e,i,o,u,bah-disgust,happy-smile. The morph-set has to be stored as vector coordinates in a relative way(offset), e.g. X1=+212,+34;X2=-56,-23;X3=+3,-88;&lt;br /&gt;
&lt;br /&gt;
To make use of the morph-set for the mouth, you have to define first, which vector points in your drawn mouth, correspond to the key-points of your morph-set. X1, X2, X3, Xn&lt;br /&gt;
&lt;br /&gt;
--[[User:SvH|SvH]] 06:53, 27 May 2008 (EDT)&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
===Render time approximation===&lt;br /&gt;
Synfigstudio should get a button in the render dialog, which calculates the total render time for the actual settings (frames per second, length of the film, resolution, output format) It should testrender 1 picture, when the amount of total frames is below 1000. Over 1000 frames, it should testrender 10 pictures for more precise calculation.&lt;br /&gt;
&lt;br /&gt;
--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
===Smartrendering===&lt;br /&gt;
I have made 25,000 small png-pictures with my 800Mhz computer in about 45 minutes. Synfigstudio did calculate each single frame of it. Nothing changed in this picture, so it does only need to get written to disk for the amount of pictures, until the next change (animation) has an effect on the output picture. This should save time for bigger projects with thousands of pictures.&lt;br /&gt;
&lt;br /&gt;
--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)   &lt;br /&gt;
&lt;br /&gt;
=== get_color method in text and radial blur ===&lt;br /&gt;
&lt;br /&gt;
[5] Without get_color method distorion produces artifacts &lt;br /&gt;
[http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1831355&amp;amp;group_id=144022&amp;amp;atid=757416 bug  1831355]. So I would like to get this problem fixed before doing something else. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== Full functional of group dialog ===&lt;br /&gt;
&lt;br /&gt;
[5] Group dialog is broken now [http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1796833&amp;amp;group_id=144022&amp;amp;atid=757416 bug 1796833]. So we should get old features work right before making new one. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== import/export .swf files ===&lt;br /&gt;
&lt;br /&gt;
very important productivity feature&lt;br /&gt;
&lt;br /&gt;
=== import/export .svg frames sequence, and/or .svg animations ===&lt;br /&gt;
&lt;br /&gt;
very important productivity feature&lt;br /&gt;
&lt;br /&gt;
=== a realtime .sif synchronized text window ===&lt;br /&gt;
&lt;br /&gt;
just like the xml editor of Inkscape, or the html editor in Dreamweaver (this is hugelly useful for productivity)&lt;br /&gt;
&lt;br /&gt;
I thinks scripting API can be implement in this way. For example you make XML DOM like implementation for python which alows to change DOM tree from python code and see chenges in canvas. By this way you can implement import/export scripts. Automation scripts. And a lot of different things. Even synchronization of animation between blender and synfig. --[[User:AkhIL|AkhIL]] 23:10, 26 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== choosing colour from gimp/inkscape palettes ===&lt;br /&gt;
&lt;br /&gt;
very useful when you need some colour comformity of what you're doing &lt;br /&gt;
&lt;br /&gt;
=== Good high-level documentation of the source code ===&lt;br /&gt;
&lt;br /&gt;
(2) It'd be nice if a newbie could quickly navigate around the source code. The best thing to do would be to add top-level comments in each file, explaining what that file does, a README.TXT in each directory, explaining what's in that directory. This would be pretty fast and easy to do, and make it much easier for new programmers to join. &lt;br /&gt;
&lt;br /&gt;
Time permitting, it would also be good to document on a high level what the data structures are, but that's harder, since those tend to evolve, and it is often difficult to keep in sync. It would also be useful to document what individual functions do (just a one-liner high-level description), but that also takes more time.&lt;br /&gt;
: There is a page link in the wiki that connect to the [http://www.synfig.com/doc Synfig API Documentation]. I think this link should be highlighted to be more accessible for newbies contributors and mature developers (the link was found [[Releases/DeveloperPreview#Support | here]]). --[[User:Genete|Genete]] 10:02, 11 December 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Mathematical functions to animate ===&lt;br /&gt;
(2/4) If you want to make a waving flag, it would be handful a sine function, tuned with random correctors, for example. &lt;br /&gt;
: -This should generate waypoints each 1, 2, 4 frames or any other step at artist's wish.&lt;br /&gt;
: -When applying a function you can add it to current values, add it to 1st frame values or simply override old values. Perhaps other options (such multiplication) would be fine, too. Something like texture editor in [http://www.artofillusion.org Art of Illusion], perhaps.&lt;br /&gt;
Perhaps it would be useful reusing the [http://www.gnu.org/software/octave/ Octave] source code to parse mathematical expressions.&lt;br /&gt;
I have rated this wish with a '2' because undoubtly many users will not be familiar to mathematical concepts, but for those who will be, I'd rate it with a 4. It would be possible to make a ball describing a parabolic moving in no time.&lt;br /&gt;
[[User:ajotatxe|ajotatxe]] 20 November 2007&lt;br /&gt;
: dooglus can probably chime in better than I here (see his example of balls on mathematical paths at http://uk.youtube.com/watch?v=YTpSfUthuVE ), but I believe that this is already possible.  Synfig does support a variety of mathematical transforms for parameters, although the way you do this is by no means intuitive.  (You might also want to check out the preambletaffy.sifz example for an easier approach to a waving flag. I know you were just using that as an example, but for the record...) [[User:Pxegeek|Pxegeek]] 00:58, 21 November 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
: I'd also rate it with a (4) (and updated the rating accordingly), not for this special case, but to make many workarounds much easier.  Simulating [Parabolic Shot|free fall], for example, would be a lot easier with real formulas.  I don't know, though how easy it will be to implement, maybe waiting for a scripting interface to be implemented is better than hacking this feature in an ad-hoc manner.  --[[User:Rubikcube|Rubikcube]] 16:38, 29 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Warning about editing bizarre things in animate editing mode ===&lt;br /&gt;
(3.5) It seems to have little sense animate certain things like Blend Method or Type of Feather. It would be very nice that the program asked comfirmation if you change these attributes in animate editing mode. If you do want to, you would have three options: &amp;quot;Yes, never ask&amp;quot;, &amp;quot;Yes, never ask for this attribute&amp;quot;, &amp;quot;No&amp;quot;. I guess that internally, this attributes has integer type (or something like that) and the attributes that you normally want to animate, float type, so I think that this feature is relatively easy to implement. My English is not very good, so please feel free to fix this post.&lt;br /&gt;
[[User:ajotatxe|ajotatxe]] 20 November 2007&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bones with FK &amp;amp; IK + grouping of objects into folders ===&lt;br /&gt;
&lt;br /&gt;
(1) Bones cane move specific vector assigned to them or the bones can have envelopes that move the vectors within their field of influence, much Like Anime Studio/Moho does. It's quite a time saving process of animating. Objects created can be saved into separate groups or folders using the same system as Anime Studio/Moho -Shadowphoenix 27/8/2007&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Animated sketch ===&lt;br /&gt;
&lt;br /&gt;
(1) it would be great, if the tool Sketch was animatable (for example, in a form of a special sketch-layer). --Zelgadis 2007-06-14&lt;br /&gt;
&lt;br /&gt;
=== Duck for Amount value in Zoom layer ===&lt;br /&gt;
&lt;br /&gt;
(2) It would be nice if Amount value in Zoom layer was controlled by additional duck. --[[User:Zelgadis|Zelgadis]] 02:49, 29 December 2007 (EST)&lt;br /&gt;
: I found that I can better use Warp layer instead of Zoom to change size. But it'd be nice to have Amount duck for Zoom layer anyway...&lt;br /&gt;
:: The Amount parameter works exponentially; each time you add 1 to the Amount, the image is zoomed by a further factor of e (= 2.71828 or so).  Would a duck be any use if it just controlled the value of Amount in a linear way?&lt;br /&gt;
:: Workarounds include: export Amount, select it in the children dialog.  Whatever's selected in the children dialog shows a duck.  You can adjust it using that duck.&lt;br /&gt;
:: Also, if you use a Stretch layer, convert the Amount to Composite, export the X-Axis and connect it to the Y-Axis, then you have a duck-controllable fixed-aspect zoom. -- [[User:Dooglus|dooglus]] 15:32, 15 January 2008 (EST)&lt;br /&gt;
::: Yeah I found this workaround, but it's to much actions - i prefer better use Warp or Stretch layers. Why not the link Amount duck and Amount value with logarithmic function? ;) --[[User:Zelgadis|Zelgadis]] 10:33, 17 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatic colour palette optimisation ===&lt;br /&gt;
&lt;br /&gt;
(0) it would be nice to use libcontrast [http://david.navi.cx/blog/?p=132] [http://david.navi.cx/blog/?p=94] [http://david.navi.cx/blog/?p=99] [http://svn.gnome.org/svn/xchat-gnome/trunk/src/libcontrast/] to automatically adjust selected or all the palette items for best visual contrast. It would also be interesting to have a layer that uses this code to filter the image.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arbitrary Color Channels ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; The ability for the user to create any number of custom channels for various purposes.&lt;br /&gt;
&lt;br /&gt;
=== Autorecover History ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; It would be great if autorecover could also recover the associated history of a file in the event of a crash.&lt;br /&gt;
&lt;br /&gt;
=== Layer Convert ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;(4)&amp;lt;/strike&amp;gt; (2) &amp;amp;mdash; The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''&lt;br /&gt;
&lt;br /&gt;
=== Vector fill bucket ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[Region Layer|region layer]]). &amp;lt;p&amp;gt;Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;If this is implemented, it will probably be necessary to change the existing &amp;quot;fill&amp;quot; tool's name and icon to a &amp;quot;color injector&amp;quot; (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.&lt;br /&gt;
&lt;br /&gt;
*Inkscape has a very innvative version of this tool. Maybe you can just grab the code from there and integrate it in synfig? --[[User:SvH|SvH]] 01:37, 14 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== [[redraw tool]] ===&lt;br /&gt;
&lt;br /&gt;
(4-5) &amp;amp;mdash; Intutive reshaping of path-based layers. See link.&lt;br /&gt;
&lt;br /&gt;
=== [http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance] ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; This should solve all complaints about the layout, without requiring Synfig to be &amp;quot;just like program (x)&amp;quot;. See [[UI Reloaded]] for progress on this.&lt;br /&gt;
&lt;br /&gt;
=== Feedback for [[Smooth Move Tool]] ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; This tool does what a lot of folks are looking for, warping selected ducks in a &amp;quot;soft&amp;quot; fashion. But it's not very obvious what sort of effect it will have, from the tool's interface. It needs some sort of momentary center-of-action and radius indicator at the very least. Perhaps an &amp;quot;influence gradient&amp;quot; overlaid on the canvas once Synfig's core is sped up?&lt;br /&gt;
&lt;br /&gt;
=== Networkability ===&lt;br /&gt;
&lt;br /&gt;
(2) &amp;amp;mdash; Like Inkscape's &amp;quot;inkboard&amp;quot; feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option. This should probably farm off all the networking stuff to the telepathy framework so that synfig doesn't have to deal with all the account/etc issues.&lt;br /&gt;
&lt;br /&gt;
=== Intuitive tangent modification ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.&lt;br /&gt;
&lt;br /&gt;
-Agreed; blender does this with its IPO curves, and it's a really efficient way to work.&lt;br /&gt;
&lt;br /&gt;
=== Plugin API ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
=== Python support ===&lt;br /&gt;
&lt;br /&gt;
(1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.&lt;br /&gt;
&lt;br /&gt;
I suuose to join this request with [[Wish_list#a_realtime_.sif_synchronized_text_window]]. We can implement python access to XML DOM and write XML Editor in python. --[[User:AkhIL|AkhIL]] 06:54, 30 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== mod_synfig ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; For Apache. Render .sif to some format like png/mng on access.&lt;br /&gt;
&lt;br /&gt;
=== synfig nsplugin ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; Let Mozilla and Mozilla-based view synfig files in-browser.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Align function ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; Align objects at a common border (as in Inkscape)&lt;br /&gt;
&lt;br /&gt;
=== Improved SVG import ===&lt;br /&gt;
&lt;br /&gt;
(4) &amp;amp;mdash; Currently, all importing an SVG does is render it in ImageMagick. What I want is the ability to import the SVG document so that all the shapes, etc. of the SVG document show up as their equivilant synfig layers - i.e. if I had put them there myself. I'm trying to write a patch for this but the codebase is mostly undocumented. [[User:KMeist|KMeist]] 16:38, 25 Feb 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
[[svg2synfig]] could be incorporated using an open source XSLT processor. --[[User:Dmd|Dmd]] 13:34, 26 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Gradient Paint Tool ===&lt;br /&gt;
&lt;br /&gt;
How about a tool that can 'paint' a gradient object.  For example the options would be width and gradient type, one would make a stroke with the tool and the gradient would be automatically applied inside of the outline (set by width).  This would save the trouble of having to the all the encapsulation stuff. (Actually any tool that makes creating gradient one step would be good).--[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bone Animation Tools ===&lt;br /&gt;
&lt;br /&gt;
Bone system with inverse kinematics, very important for quick animation. You put bones on a drawed man and you can animate him like a puppet. I'm using that in Moho (lost marble product).--[[User:Ziolive|ziolive]] 23 Aug 2006&lt;br /&gt;
*I would find this very useful too. I think it is called '''rigging'''(4/5) --[[User:SvH|SvH]] 01:33, 14 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== AVI Backgrounds ===&lt;br /&gt;
Is there any way I can add an avi as a background so I could add facial expressions to a stop-motion animated figure. [zotz here, I was thinking DV background or extra timeline. I would like to mix animations with live footage. rating (3/4)]&lt;br /&gt;
&lt;br /&gt;
=== Character tool on Tool Options Dialog ===&lt;br /&gt;
&lt;br /&gt;
I want to use the as a character generator for a TV show. By using chroma key hide the background.  Even better interface to a video overlay card with Alpha blending.&lt;br /&gt;
&lt;br /&gt;
=== Collect for Publication ===&lt;br /&gt;
&lt;br /&gt;
(3/4) - (zotz) Menu item, functionality that would collect alll files referenced in a sif and place them all in a tgz for sending elsewhere or publishing anumations in source form.&lt;br /&gt;
&lt;br /&gt;
=== Object Library ===&lt;br /&gt;
&lt;br /&gt;
(3/4) - (zotz) Haven't thought this all through yet, but synfig could come with a library of categotrised &amp;quot;objects&amp;quot; with a copyleft license (GPL?  CC BY-SA?) An animation clip art type deal.&lt;br /&gt;
**I'd suggest this should be public domain and distributed by openclipart.org -- --[[User:PaulWise|pabs]]&lt;br /&gt;
&lt;br /&gt;
=== Flash Export ===&lt;br /&gt;
&lt;br /&gt;
(3/4) Well, might just be me but if there was a posiblity to  export in .swf or .fla, I think the project might become a lot more popular.[[User:Conceit|Conceit]]&lt;br /&gt;
&lt;br /&gt;
(4/5) I wholeheartedly agree. I would definitely use synfig more if this feature were added and it would most definitely increase popularity. [[User:cdj05a|cdj05a]]&lt;br /&gt;
&lt;br /&gt;
=== Single window ===&lt;br /&gt;
&lt;br /&gt;
Depending on individual desktop setups, single window is sometimes preferable to many  windows. Can we have a single-window option?&lt;br /&gt;
&lt;br /&gt;
Also, even with many windows, Windows-users especially might find it better if all the windows only appeared as a single one on the taskbar.&lt;br /&gt;
&lt;br /&gt;
=== Line width tool ===&lt;br /&gt;
(4) It will be good to have a tool for easy changing line width. There was a such tool in earlier versions, but it's not usable. I'm often use variable line width, when drawing in synfig, so it is important for me. -- [[User:Zelgadis|Zelgadis]] 2007-09-09&lt;br /&gt;
&lt;br /&gt;
: It is [[FAQ#Where did the polygon, draw, sketch, and width tools go?|still available]].  Also, you can turn on the width ducks, using Alt-5. -- [[User:Dooglus|dooglus]] 12:18, 9 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
:: It is available, but I never was able to figure out how it works. Alt-5 works, but it is hard to set width to zero, for example. -- [[User:Zelgadis|Zelgadis]] 2007-09-10&lt;br /&gt;
&lt;br /&gt;
::: Are you wanting something that works on one vertex at a time?  Or all the vertices in an area?  Apparently the width tool was designed to work on a bunch of vertices at once.  I didn't figure out how it works though, either. -- [[User:Dooglus|dooglus]] 16:57, 10 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
:::: Width tool is surely a mystery. :) I'm waiting for something that works on one vertex at time. I liked the way as width was changed in Moho (Anime Studio now) - there was a special width tool and holding left mouse button on the vertex and moving cursor left decreasing width value, moving right - increasing. Maybe it make sense to rework Width tool in such way. -- [[User:Zelgadis|Zelgadis]] 2007-09-13&lt;br /&gt;
&lt;br /&gt;
::In my opinion the use of a seperate device like a joystick could help. You draw the line with the mouse and with the other hand, you push/pull the joystick to change the linewith in realtime. --[[User:SvH|SvH]] 05:25, 30 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== Export Wizard ===&lt;br /&gt;
&lt;br /&gt;
(2/4) Conversion and export to other file formats (mpg, avi, flash formats, others, and the synfig format) with a step by step wizard for choosing format and place of saving. Similar to Gimp's saving of .png files but for movie/video type files. --&lt;br /&gt;
[[User:Hiddenghost|hiddenghost]]&lt;br /&gt;
&lt;br /&gt;
=== Using Synfig as a portable app ===&lt;br /&gt;
&lt;br /&gt;
(3) This isn't really a feature request (though it could be) but I was wondering if synfig could be used as a portable application (as in www.portableapps.com). Does the windows install require registry access? i really want to use Synfig at work, but I'm reluctant to install it just in case it leave footprints in the regisitry or something, and it would be sweet to use it on my travels as well. Only thing is, I can't test it out at home because I am using Linux.&lt;br /&gt;
See also: http://portableapps.com/node/5761&lt;br /&gt;
[[User:Zenoscope|zenoscope]]&lt;br /&gt;
&lt;br /&gt;
This isn't currently possible without modifying the source code. That has been on my TODO list for ages [[User:PaulWise|pabs]] 01:17, 26 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Allow organize child valuenodes in an hierarchy ===&lt;br /&gt;
(3-2) And allow maintain the organization once the file is saved. At the moment they are reordered in alphabetical order which is useless and annoying.&lt;br /&gt;
&lt;br /&gt;
=== Triangle sliders to be always visible ===&lt;br /&gt;
(3) I would like that the triangle sliders from [[Colors Dialog]] and [[Gradient Editor Dialog]] were visible whatever color or channel you're editing. Some times when the color or channel is to bright or light the slider is difficult to distinguish. --[[User:Genete|Genete]] 14:30, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== XICC support ===&lt;br /&gt;
&lt;br /&gt;
It would be cool if synfigstudio had support for [http://burtonini.com/blog/computers/xicc XICC].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Area to Edit ===&lt;br /&gt;
&lt;br /&gt;
An option like blender - select area to update would be nice, so the only part of the image that updates when you add or change something is in the selected area&lt;br /&gt;
&lt;br /&gt;
ie. when working on a complex composition, studio doesn't know, when I tweak a tiny part of the composition, that only that part needs redrawing, so it redraws the whole thing.  It would be good if there was some way of telling it which part to focus on. -- [[User:Dooglus|dooglus]] 04:02, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Histograms ===&lt;br /&gt;
&lt;br /&gt;
 01:23  * AkhIL wish to have histograms and luma/color scope like [http://mac.softpedia.com/progScreenshots/Avid-Xpress-DV-Screenshot-14207.html] in synfig&lt;br /&gt;
&lt;br /&gt;
I've looked at those pictures but don't know what they're showing.  Can you describe what those scopes are doing, and what the histograms display?  ie. what are the X and Y axes of the histograms? -- [[User:Dooglus|dooglus]] 04:07, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
First look this description in blender wiki [http://wiki.blender.org/index.php/Manual/VSE_Modes]&lt;br /&gt;
&lt;br /&gt;
Ok There is four things.&lt;br /&gt;
* Upper left is Lumascope (Luma Waveform in blender). X-Axis represents image's X-Axys. Y-Axis  is average luminescence of column of pixels.&lt;br /&gt;
* Upper right is Chromascope (Chroma Vectorscope in blender). Just look description on blender wiki.&lt;br /&gt;
* Lower left is like Lumascope but for each channel &lt;br /&gt;
* Lower right is histograms. X is luminescence and Y is count of pixels with such luminiscence.&lt;br /&gt;
&lt;br /&gt;
=== Sound Layer ===&lt;br /&gt;
&lt;br /&gt;
(4) It would be a very good improvement if the sound system were implemented into synfig in [[Sound Layer | this]] way. --[[User:Genete|Genete]] 07:46, 8 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Rearrange the view of waypoints for Canvas param ===&lt;br /&gt;
As reported in [http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1888858&amp;amp;group_id=144022&amp;amp;atid=757416 Bug #1888858] waypoints are not displayed for canvas switch events.&lt;br /&gt;
I suggest to rearrange waypoints display according to [[Media:Canvas_prop.png|this scheme]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Width weigths ===&lt;br /&gt;
Is it possible to add &amp;quot;weigths&amp;quot; for widths? ^_^ I.e. width changes not all the way along the segment. Maybe something like a duck on bline which indicates the region where the width of current vertex isn't changed.&lt;br /&gt;
[[Media:width-proposal.png|Illustration here.]]&lt;br /&gt;
&lt;br /&gt;
More ideas around this concept in [http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-04-16.log this conversation]. Although the log of that day is very interesting the lines related to this idea are from 22:38 to 23:43. [[User:Genete|Genete]] 17:51, 16 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Improved Colour Dialog ===&lt;br /&gt;
How easy is it to stick in a colour square/wheel? Messing with sliders is somewhat obstructive.&lt;br /&gt;
&lt;br /&gt;
=== Insert Waypoints ===&lt;br /&gt;
A button to create a waypoint for every selected duck, in its current position. Moving each duck up a bit and down again quickly gets tedious.&lt;br /&gt;
:If the duck in question has already a waypoint then you don't need to move it to create a new waypoint. Just select the corresponding parameter in your child list panel and select 'Add Waypoint' from the right click context menu over the parameter. No need to have the duck selected. If you want to freeze the entire bline just do that over the Bline Point List. [[User:Genete|Genete]] 07:48, 29 April 2008 (EDT)&lt;br /&gt;
::Yes, but it would be nice to have opportunity to add waypoint to parameer which not have any ducks yet (i.e. non-animated parameter). --[[User:Zelgadis|Zelgadis]] 08:33, 29 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatically split tangeants ===&lt;br /&gt;
&lt;br /&gt;
Holding shift while moving tangeant ducks should automatically split them. They can be rejoined if necessary through the context menu as they are now.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7191</id>
		<title>Roadmap</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7191"/>
				<updated>2008-05-28T17:03:42Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Easy coding tasks */ usage screen&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
This page contains a roadmap with defined goals for each release. See [[Software roadmap]] for things we want to do with synfig at some point. See [[Release]] for the process we go through when releasing.&lt;br /&gt;
&lt;br /&gt;
As an open source project, synfig is relatively young. As a result, it has lots of creases that need to be ironed out. The copyright is sorted, the code compiles fine, but there are warts when running the code. To smooth out those warts, we need people do investigate and fix the following. We cannot do everything ourselves, WE NEED YOUR HELP!!&lt;br /&gt;
&lt;br /&gt;
== Tasks, to reach a final version of 1.0 ==&lt;br /&gt;
&lt;br /&gt;
=== 0.7 ===&lt;br /&gt;
* Synfigstudio needs a man page&lt;br /&gt;
&lt;br /&gt;
=== 0.8 ===&lt;br /&gt;
&lt;br /&gt;
=== 0.9 ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Things, which are also accepted in our patch tracker==&lt;br /&gt;
&lt;br /&gt;
* create better builds for MacOS X.&lt;br /&gt;
* fixes for any of the open [[Bugs|bugs]].&lt;br /&gt;
* embedded source code documentation&lt;br /&gt;
* Write a tutorial&lt;br /&gt;
* translate into your language&lt;br /&gt;
* test synfig and confirm open bugs&lt;br /&gt;
&lt;br /&gt;
=== Easy coding tasks ===&lt;br /&gt;
Put here tasks for new developers, to make them able to dive into the code.&lt;br /&gt;
&lt;br /&gt;
* Synfigstudio needs verbosity levels for the error output. Levels are info, warning and error. Make sure, to spew out only errors when something nasty happens. If someone wants to know all what happens in synfigstudio, the user should activate a higher level of verbosity with the command line switch --verbose=all,info,warning&lt;br /&gt;
&lt;br /&gt;
* Synfig and Synfigstudio need a usage screen, which helps a new user to type in the right syntax on the command line. Any switch not known to the program should point to the usage screen. On the bottom of the usage screen could be a hint: &amp;quot; For more help use synfig --help&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==To the old [[Releases]]==&lt;br /&gt;
&lt;br /&gt;
Just for reference.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7190</id>
		<title>Roadmap</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7190"/>
				<updated>2008-05-28T15:13:47Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* 0.7 */ man page for synfigstudio&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
This page contains a roadmap with defined goals for each release. See [[Software roadmap]] for things we want to do with synfig at some point. See [[Release]] for the process we go through when releasing.&lt;br /&gt;
&lt;br /&gt;
As an open source project, synfig is relatively young. As a result, it has lots of creases that need to be ironed out. The copyright is sorted, the code compiles fine, but there are warts when running the code. To smooth out those warts, we need people do investigate and fix the following. We cannot do everything ourselves, WE NEED YOUR HELP!!&lt;br /&gt;
&lt;br /&gt;
== Tasks, to reach a final version of 1.0 ==&lt;br /&gt;
&lt;br /&gt;
=== 0.7 ===&lt;br /&gt;
* Synfigstudio needs a man page&lt;br /&gt;
&lt;br /&gt;
=== 0.8 ===&lt;br /&gt;
&lt;br /&gt;
=== 0.9 ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Things, which are also accepted in our patch tracker==&lt;br /&gt;
&lt;br /&gt;
* create better builds for MacOS X.&lt;br /&gt;
* fixes for any of the open [[Bugs|bugs]].&lt;br /&gt;
* embedded source code documentation&lt;br /&gt;
* Write a tutorial&lt;br /&gt;
* translate into your language&lt;br /&gt;
* test synfig and confirm open bugs&lt;br /&gt;
&lt;br /&gt;
=== Easy coding tasks ===&lt;br /&gt;
Put here tasks for new developers, to make them able to dive into the code.&lt;br /&gt;
&lt;br /&gt;
* Synfigstudio needs verbosity levels for the error output. Levels are info, warning and error. Make sure, to spew out only errors when something nasty happens. If someone wants to know all what happens in synfigstudio, the user should activate a higher level of verbosity with the command line switch --verbose=all,info,warning&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==To the old [[Releases]]==&lt;br /&gt;
&lt;br /&gt;
Just for reference.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7189</id>
		<title>Roadmap</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7189"/>
				<updated>2008-05-28T15:08:16Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
&lt;br /&gt;
This page contains a roadmap with defined goals for each release. See [[Software roadmap]] for things we want to do with synfig at some point. See [[Release]] for the process we go through when releasing.&lt;br /&gt;
&lt;br /&gt;
As an open source project, synfig is relatively young. As a result, it has lots of creases that need to be ironed out. The copyright is sorted, the code compiles fine, but there are warts when running the code. To smooth out those warts, we need people do investigate and fix the following. We cannot do everything ourselves, WE NEED YOUR HELP!!&lt;br /&gt;
&lt;br /&gt;
== Tasks, to reach a final version of 1.0 ==&lt;br /&gt;
&lt;br /&gt;
=== 0.7 ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 0.8 ===&lt;br /&gt;
&lt;br /&gt;
=== 0.9 ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Things, which are also accepted in our patch tracker==&lt;br /&gt;
&lt;br /&gt;
* create better builds for MacOS X.&lt;br /&gt;
* fixes for any of the open [[Bugs|bugs]].&lt;br /&gt;
* embedded source code documentation&lt;br /&gt;
* Write a tutorial&lt;br /&gt;
* translate into your language&lt;br /&gt;
* test synfig and confirm open bugs&lt;br /&gt;
&lt;br /&gt;
=== Easy coding tasks ===&lt;br /&gt;
Put here tasks for new developers, to make them able to dive into the code.&lt;br /&gt;
&lt;br /&gt;
* Synfigstudio needs verbosity levels for the error output. Levels are info, warning and error. Make sure, to spew out only errors when something nasty happens. If someone wants to know all what happens in synfigstudio, the user should activate a higher level of verbosity with the command line switch --verbose=all,info,warning&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==To the old [[Releases]]==&lt;br /&gt;
&lt;br /&gt;
Just for reference.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7188</id>
		<title>Roadmap</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7188"/>
				<updated>2008-05-28T15:02:54Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: put the best ideas from the wishes and the bugs here.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains a roadmap with defined goals for each release. See [[Software roadmap]] for things we want to do with synfig at some point. See [[Release]] for the process we go through when releasing.&lt;br /&gt;
&lt;br /&gt;
As an open source project, synfig is relatively young. As a result, it has lots of creases that need to be ironed out. The copyright is sorted, the code compiles fine, but there are warts when running the code. To smooth out those warts, we need people do investigate and fix the following. We cannot do everything ourselves, WE NEED YOUR HELP!!&lt;br /&gt;
&lt;br /&gt;
== Tasks, which need to be done to reach a final version of 1.0 ==&lt;br /&gt;
&lt;br /&gt;
=== 0.7 ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== 0.8 ===&lt;br /&gt;
&lt;br /&gt;
=== 0.9 ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Things, which are also accepted in our patch tracker==&lt;br /&gt;
&lt;br /&gt;
* create better builds for MacOS X.&lt;br /&gt;
* fixes for any of the open [[Bugs|bugs]].&lt;br /&gt;
* embedded source code documentation&lt;br /&gt;
* Write a tutorial&lt;br /&gt;
* translate into your language&lt;br /&gt;
* test synfig and confirm open bugs&lt;br /&gt;
&lt;br /&gt;
=== Easy coding tasks ===&lt;br /&gt;
Put here tasks for new developers, to make them able to dive into the code.&lt;br /&gt;
&lt;br /&gt;
* Synfigstudio needs verbosity levels for the error output. Levels are info, warning and error. Make sure, to spew out only errors when something nasty happens. If someone wants to know all what happens in synfigstudio, the user should activate a higher level of verbosity with the command line switch --verbose=all,info,warning&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==To the old [[Releases]]==&lt;br /&gt;
&lt;br /&gt;
Just for reference.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Releases/0.61.06&amp;diff=7187</id>
		<title>Releases/0.61.06</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Releases/0.61.06&amp;diff=7187"/>
				<updated>2008-05-28T14:42:18Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Synfig 0.61.06 */ moved from Roadmap&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Synfig 0.61.06 =&lt;br /&gt;
&lt;br /&gt;
Sunday, June 24, 2007 by pabs&lt;br /&gt;
&lt;br /&gt;
We've finally managed to squeeze out a new release. This one is mainly focussed on bug fixes (thanks to dooglus mostly) and a few new features. There are also some pretty new icons in the GUI done by PXEGeek.&lt;br /&gt;
&lt;br /&gt;
As usual, we need your help. If you know C++, are an artist, can document things or are willing to learn, please join the mailing lists and IRC channel and start helping out.&lt;br /&gt;
&lt;br /&gt;
Be on the lookout for an announcement about an IRC &amp;amp; gobby meeting that will happen soon.&lt;br /&gt;
&lt;br /&gt;
Read on for some of the changes that were made...&lt;br /&gt;
&lt;br /&gt;
ETL 0.04.09 (SVN 530) - June 20, 2006 - Bug fixes&lt;br /&gt;
&lt;br /&gt;
* Fix amd64 issue&lt;br /&gt;
* Some tests fixes&lt;br /&gt;
* Misc bug fixes&lt;br /&gt;
* Add better code for finding closest point to a bezier (#1672033)&lt;br /&gt;
&lt;br /&gt;
synfig 0.61.06 (SVN 536) - June 20, 2007 - Bug fixes&lt;br /&gt;
&lt;br /&gt;
* Add fontconfig support&lt;br /&gt;
* Fix amd64 issue&lt;br /&gt;
* Fix ffmpeg, gif, libav targets&lt;br /&gt;
* Include more target modules in the Win32 package&lt;br /&gt;
* Fix some crashes in synfigstudio&lt;br /&gt;
* Fix some render artifacts&lt;br /&gt;
* Fix some doxygen warnings&lt;br /&gt;
* Some MacOS fixes&lt;br /&gt;
* Misc bug fixes&lt;br /&gt;
* Fix random number generation for 64 bit CPUs (#1698604)&lt;br /&gt;
* Add parameter 'fast' to curve gradients allowing choice between fast or accurate rendering (#1672033)&lt;br /&gt;
* Add new odd/even winding style for regions&lt;br /&gt;
&lt;br /&gt;
synfigstudio 0.61.06 (SVN 543) - June 20, 2007 - Bug fixes&lt;br /&gt;
&lt;br /&gt;
* Fix amd64 issues&lt;br /&gt;
* Fix corruption of gamma settings&lt;br /&gt;
* Fix manipulating layers in the layer dialog&lt;br /&gt;
* Disable the timebar instead of hiding it&lt;br /&gt;
* Fix File -&amp;gt; Close &amp;amp; input devices close button&lt;br /&gt;
* Fix targets that crash in synfigstudio&lt;br /&gt;
* Fix some doxygen warnings&lt;br /&gt;
* Fixes in the sketch tool&lt;br /&gt;
* Fixes in the draw tool&lt;br /&gt;
* Fix several crashes&lt;br /&gt;
* Fix bline looping&lt;br /&gt;
* Misc Win32 fixes&lt;br /&gt;
* Add optional GNOME thumbnailer&lt;br /&gt;
* Rework several dialogs to use GNOME HIG&lt;br /&gt;
* Disable several tools, see FAQ to re-enable&lt;br /&gt;
* Disable the empty Palette Browser dialog&lt;br /&gt;
* Add mousewheel support in canvas windows&lt;br /&gt;
* Add tooltips to preview window &amp;amp; give it a default size&lt;br /&gt;
* Display HTML values in the colour dialog&lt;br /&gt;
* Add an icon for the curves dialog&lt;br /&gt;
* New Tango ArtLibreSet styled icons by PXEGeek&lt;br /&gt;
&lt;br /&gt;
== synfig 0.61.06 ==&lt;br /&gt;
&lt;br /&gt;
* Fix the synfigstudio's icon finding and SYNFIG_ROOT stuff - [http://sf.net/support/tracker.php?aid=1568925 1568925]&lt;br /&gt;
* Fix the touchpad/mouse/Input Devices issue;  It's initially very off putting when you can't draw even a single circle - [http://sf.net/support/tracker.php?aid=1677510 1677510]&lt;br /&gt;
* Fix the uninstall in the Windows packages, and also make a single download available - [http://sf.net/support/tracker.php?aid=1673269 1673269]&lt;br /&gt;
* fix the synfig rendering targets that crash (gif, dv, ffmpeg, imagemagick).&amp;lt;br&amp;gt;Bugs: [http://sf.net/support/tracker.php?aid=1346746 1346746] [http://sf.net/support/tracker.php?aid=1480722 1480722] ...&lt;br /&gt;
* create better builds for Windows.&lt;br /&gt;
* fix miscompilation of synfig with g++ 4.1.x and g++ 4.2&amp;lt;br&amp;gt;Bugs: [http://sf.net/support/tracker.php?aid=1509627 1509627] [http://bugs.debian.org/375080 DEB375080]&lt;br /&gt;
* fix synfig OOM when rendering the synfigstudio images on non-intel platforms.&amp;lt;br&amp;gt;Bugs: [http://sf.net/support/tracker.php?aid=1497893 1497893] [http://bugs.debian.org/369646 DEB369646]&lt;br /&gt;
* fix synfigstudio so that the toolbox window is shown on the taskbar/panel when no image is open.&amp;lt;br&amp;gt;Bugs: [http://bugs.debian.org/366731 DEB366731]&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7186</id>
		<title>Roadmap</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7186"/>
				<updated>2008-05-28T14:41:14Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* synfig 0.61.06 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains a roadmap with defined goals for each release. See [[Software roadmap]] for things we want to do with synfig at some point. See [[Release]] for the process we go through when releasing.&lt;br /&gt;
&lt;br /&gt;
As an open source project, synfig is relatively young. As a result, it has lots of creases that need to be ironed out. The copyright is sorted, the code compiles fine, but there are warts when running the code. To smooth out those warts, we need people do investigate and fix the following. We cannot do everything ourselves, WE NEED YOUR HELP!!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Tasks which are also accepted from fresh developers in our patch tracker==&lt;br /&gt;
&lt;br /&gt;
* create better builds for MacOS X.&lt;br /&gt;
** Bugs: [http://sf.net/support/tracker.php?aid=1686495 1686495]&lt;br /&gt;
** Solutions:&lt;br /&gt;
*** make synfig installation relocatable and more robust&lt;br /&gt;
*** come up with a solution for the gtk stuff.&lt;br /&gt;
* fix the rest of the regressions, crashes, freezes and compile errors.&lt;br /&gt;
** Bugs: &lt;br /&gt;
** Solution: more debugging&lt;br /&gt;
* fixes for any of the open [[Bugs|bugs]].&lt;br /&gt;
* embedded source code documentation&lt;br /&gt;
* almost anything else&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Old realeases =&lt;br /&gt;
==[[Releases]]==&lt;br /&gt;
&lt;br /&gt;
Move releases here when they are done.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Releases/0.61.07&amp;diff=7185</id>
		<title>Releases/0.61.07</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Releases/0.61.07&amp;diff=7185"/>
				<updated>2008-05-28T14:40:14Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: moved from Roadmap&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Synfig 0.61.07 =&lt;br /&gt;
&lt;br /&gt;
Tuesday, October 9, 2007 by dooglus&lt;br /&gt;
&lt;br /&gt;
At long last, we have a new release! There have been lots of changes since the last release 4 months ago. This release fixes lots of bugs, and adds a few minor new features. Overall stability should be much improved, but you still need to apply a [[FAQ#Can_I_do_anything_to_improve_the_stability_of_the_Windows_version_of_Synfig.3F|workaround]] to get decent stability on multi-core Windows machines.&lt;br /&gt;
&lt;br /&gt;
The source code is available for [http://sf.net/project/showfiles.php?group_id=144022&amp;amp;package_id=198849 ETL], [http://sf.net/project/showfiles.php?group_id=144022&amp;amp;package_id=158279 synfig], and [http://sf.net/project/showfiles.php?group_id=144022&amp;amp;package_id=198850 synfigstudio]. Windows binaries are also available on the [[Download|download page]].&lt;br /&gt;
&lt;br /&gt;
Read on for the list of changes since the last release.&lt;br /&gt;
&lt;br /&gt;
ETL 0.04.10 - Bug fixes&lt;br /&gt;
&lt;br /&gt;
* Fix dirname for absolute paths ([http://sf.net/support/tracker.php?aid=1793306 #1793306])&lt;br /&gt;
* Fix minor issues and typos&lt;br /&gt;
* Various changes to the 'angle' code. 89+360 &amp;lt; 90; 90 == 90+360, !360 is true, etc.&lt;br /&gt;
* Resolve confusion about whether angles are clockwise, and whether they're stored in radians.&lt;br /&gt;
* Fix 'make check' for 'fixed' so that it doesn't fail. Tidy the output, too.&lt;br /&gt;
&lt;br /&gt;
synfig 0.61.07&lt;br /&gt;
&lt;br /&gt;
* Fix importing on amd64 ([http://sf.net/support/tracker.php?aid=1692825 #1692825])&lt;br /&gt;
* Fixes for the PasteCanvas layer ([http://sf.net/support/tracker.php?aid=1356449 #1356449])&lt;br /&gt;
* Clean up Layer menu and displayed layer names&lt;br /&gt;
* Allow exported canvases to be used in more than one place within a canvas ([http://sf.net/support/tracker.php?aid=1785296 #1785296])&lt;br /&gt;
* Fix, extend, and enable the 'XOR Pattern' layer&lt;br /&gt;
* Fix and extend the 'Plant' layer ([http://sf.net/support/tracker.php?aid=1790903 #1790903])&lt;br /&gt;
* Turn on plant layer (gunsmoke) in macwolfen.sifz example&lt;br /&gt;
* Use 'fast gaussian' rather than 'gaussian' for blurs in pirates.sifz - it's faster!&lt;br /&gt;
* Fix and enable the 'Timed Swap' valuenode conversion&lt;br /&gt;
* Extend the 'Linear' valuenode conversion to work with colors and integers.&lt;br /&gt;
* Enable basic motion blur display at all qualities&lt;br /&gt;
* Fix an artifact on the curve gradient layer ([http://sf.net/support/tracker.php?aid=1792063 #1792063]&lt;br /&gt;
* Add the 'Range', 'Repeat Gradient', 'Add', 'Exponent' valuenode conversions&lt;br /&gt;
* Add the 'BLine Vector', and 'BLine Tangent' valuenode conversions ([http://sf.net/support/tracker.php?aid=1781903 #1781903])&lt;br /&gt;
* Fix problems with valuenode conversion ([http://sf.net/support/tracker.php?aid=1794374 #1794374], [http://sf.net/support/tracker.php?aid=1795913 #1795913], [http://sf.net/support/tracker.php?aid=1795922 #1795922], [http://sf.net/support/tracker.php?aid=1796068 #1796068], [http://sf.net/support/tracker.php?aid=1797488 #1797488])&lt;br /&gt;
* Allow gradients to be animated ([http://sf.net/support/tracker.php?aid=1568818 #1568818], [http://sf.net/support/tracker.php?aid=1795802 #1795802])&lt;br /&gt;
* Stop TCB angle waypoints changing to type Linear on load ([http://sf.net/support/tracker.php?aid=1778930 #1778930])&lt;br /&gt;
* Use compression when saving to files with .sifz extension&lt;br /&gt;
* Compressed example .sif files to .sifz to save space&lt;br /&gt;
* Fixed Motion Blur layer ([http://sf.net/support/tracker.php?aid=1800783 #1800783])&lt;br /&gt;
* Allow building studio with gcc -O2 ([http://sf.net/support/tracker.php?aid=1509627 #1509627])&lt;br /&gt;
* Allow encapsulated layers to animate their z-depth, even when time-shifted ([http://sf.net/support/tracker.php?aid=1806852 #1806852])&lt;br /&gt;
* Fixed the Radial Blur layer when zooming in on the canvas ([http://sf.net/support/tracker.php?aid=1807709 #1807709])&lt;br /&gt;
* Fix several other bugs and crashes&lt;br /&gt;
&lt;br /&gt;
synfigstudio 0.61.07&lt;br /&gt;
&lt;br /&gt;
* Fix some tooltips and menu stuff ([http://sf.net/support/tracker.php?aid=1787437 #1787437])&lt;br /&gt;
* Allow left-right scrolling in canvas window with shift + mouse-wheel&lt;br /&gt;
* Rework mouse interaction with ducks and tangents&lt;br /&gt;
* Move icons to a subdir&lt;br /&gt;
* Fix some typos, several crashes ([http://sf.net/support/tracker.php?aid=1780016 #1780016], [http://sf.net/support/tracker.php?aid=1785598 #1785598]) and other bugs&lt;br /&gt;
* Re-enable sketch, draw, polygon by default&lt;br /&gt;
* Add [[Keyboard Shortcuts|keyboard shortcuts]] for all tools&lt;br /&gt;
* Fix crash when setting canvas resolution to zero ([http://sf.net/support/tracker.php?aid=1779616 #1779616])&lt;br /&gt;
* Add 'auto-export' checkbox and layer name box to the draw tool&lt;br /&gt;
* Various GUI fixes ([http://sf.net/support/tracker.php?aid=1794006 #1794006], [http://sf.net/support/tracker.php?aid=1796110 #1796110])&lt;br /&gt;
* File-selector fixes ([http://sf.net/support/tracker.php?aid=1383736 #1383736])&lt;br /&gt;
* Fix the View&amp;gt;Play menu entry to allow playback inside the workarea, shortcut Ctrl-P&lt;br /&gt;
* Save to .sifz (compressed) format by default if no extension is given&lt;br /&gt;
* Remember the path used when saving a document and default to it in future&lt;br /&gt;
* Call new documents &amp;quot;Synfig Animation &amp;quot; by default, rather than &amp;quot;untitled0&amp;quot;&lt;br /&gt;
* Don't quit until the user clearly answers &amp;quot;do you want to save?&amp;quot; ([http://sf.net/support/tracker.php?aid=1799722 #1799722])&lt;br /&gt;
* Remember the filename the animation was last rendered to, and default to it ([http://sf.net/support/tracker.php?aid=1799250 #1799250])&lt;br /&gt;
* Improved the 'Groups' function a little ([http://sf.net/support/tracker.php?aid=1368694 #1368694]). It's still quite broken&lt;br /&gt;
* Fixed the colors displayed on the sliders in the Color Editor dialog&lt;br /&gt;
* Added option to Bline Tool to allow positions to be automatically linked ([http://sf.net/support/tracker.php?aid=1776156 #1776156])&lt;br /&gt;
* Added menu entry to restore all dialogs to their default positions&lt;br /&gt;
* Fix red &amp;quot;Animate Editing Mode&amp;quot; frame so it shows up in all themes ([http://sf.net/support/tracker.php?aid=1801220 #1801220])&lt;br /&gt;
* Allow user to &amp;quot;export SYNFIG_DISABLE_POPUP_WINDOWS=1&amp;quot; to make splash screen etc. less obtrusive&lt;br /&gt;
* Fixed the logic used to decide which value to use when linking values together&lt;br /&gt;
* Update child canvas time sliders when parent time slider is moved&lt;br /&gt;
* Prevent the caret menu entries from being disabled when another canvas is closed&lt;br /&gt;
* Show the correct initial quality level in the View &amp;gt; Preview Quality menu&lt;br /&gt;
&lt;br /&gt;
== synfig 0.61.07 ==&lt;br /&gt;
&lt;br /&gt;
Crashes:&lt;br /&gt;
&lt;br /&gt;
* Fixed crash rendering http://dooglus.rincevent.net/synfig/crasher3.sif&lt;br /&gt;
* Fixed crash creating new paste canvas layers ([http://sf.net/support/tracker.php?aid=1356449 1356449])&lt;br /&gt;
* Fixed crash with relative pathnames ([http://sf.net/support/tracker.php?aid=1383736 1383736])&lt;br /&gt;
* Fixed disconnect bug [http://sf.net/support/tracker.php?aid=1356376 1356376] ...&lt;br /&gt;
Other:&lt;br /&gt;
&lt;br /&gt;
* Fixed importing images on amd64 ([http://sf.net/support/tracker.php?aid=1692825 1692825])&lt;br /&gt;
* Moved pixmaps to a subdir&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7184</id>
		<title>Roadmap</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7184"/>
				<updated>2008-05-28T14:38:21Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Completed */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains a roadmap with defined goals for each release. See [[Software roadmap]] for things we want to do with synfig at some point. See [[Release]] for the process we go through when releasing.&lt;br /&gt;
&lt;br /&gt;
As an open source project, synfig is relatively young. As a result, it has lots of creases that need to be ironed out. The copyright is sorted, the code compiles fine, but there are warts when running the code. To smooth out those warts, we need people do investigate and fix the following. We cannot do everything ourselves, WE NEED YOUR HELP!!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Tasks which are also accepted from fresh developers in our patch tracker==&lt;br /&gt;
&lt;br /&gt;
* create better builds for MacOS X.&lt;br /&gt;
** Bugs: [http://sf.net/support/tracker.php?aid=1686495 1686495]&lt;br /&gt;
** Solutions:&lt;br /&gt;
*** make synfig installation relocatable and more robust&lt;br /&gt;
*** come up with a solution for the gtk stuff.&lt;br /&gt;
* fix the rest of the regressions, crashes, freezes and compile errors.&lt;br /&gt;
** Bugs: &lt;br /&gt;
** Solution: more debugging&lt;br /&gt;
* fixes for any of the open [[Bugs|bugs]].&lt;br /&gt;
* embedded source code documentation&lt;br /&gt;
* almost anything else&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Old realeases =&lt;br /&gt;
==[[Releases]]==&lt;br /&gt;
&lt;br /&gt;
Move releases here when they are done.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== synfig 0.61.06 ==&lt;br /&gt;
&lt;br /&gt;
* Fix the synfigstudio's icon finding and SYNFIG_ROOT stuff - [http://sf.net/support/tracker.php?aid=1568925 1568925]&lt;br /&gt;
* Fix the touchpad/mouse/Input Devices issue;  It's initially very off putting when you can't draw even a single circle - [http://sf.net/support/tracker.php?aid=1677510 1677510]&lt;br /&gt;
* Fix the uninstall in the Windows packages, and also make a single download available - [http://sf.net/support/tracker.php?aid=1673269 1673269]&lt;br /&gt;
* fix the synfig rendering targets that crash (gif, dv, ffmpeg, imagemagick).&amp;lt;br&amp;gt;Bugs: [http://sf.net/support/tracker.php?aid=1346746 1346746] [http://sf.net/support/tracker.php?aid=1480722 1480722] ...&lt;br /&gt;
* create better builds for Windows.&lt;br /&gt;
* fix miscompilation of synfig with g++ 4.1.x and g++ 4.2&amp;lt;br&amp;gt;Bugs: [http://sf.net/support/tracker.php?aid=1509627 1509627] [http://bugs.debian.org/375080 DEB375080]&lt;br /&gt;
* fix synfig OOM when rendering the synfigstudio images on non-intel platforms.&amp;lt;br&amp;gt;Bugs: [http://sf.net/support/tracker.php?aid=1497893 1497893] [http://bugs.debian.org/369646 DEB369646]&lt;br /&gt;
* fix synfigstudio so that the toolbox window is shown on the taskbar/panel when no image is open.&amp;lt;br&amp;gt;Bugs: [http://bugs.debian.org/366731 DEB366731]&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7183</id>
		<title>Roadmap</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Roadmap&amp;diff=7183"/>
				<updated>2008-05-28T14:34:44Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* synfig ?.??.?? */ cleanup a bit&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains a roadmap with defined goals for each release. See [[Software roadmap]] for things we want to do with synfig at some point. See [[Release]] for the process we go through when releasing.&lt;br /&gt;
&lt;br /&gt;
As an open source project, synfig is relatively young. As a result, it has lots of creases that need to be ironed out. The copyright is sorted, the code compiles fine, but there are warts when running the code. To smooth out those warts, we need people do investigate and fix the following. We cannot do everything ourselves, WE NEED YOUR HELP!!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Tasks which are also accepted from fresh developers in our patch tracker==&lt;br /&gt;
&lt;br /&gt;
* create better builds for MacOS X.&lt;br /&gt;
** Bugs: [http://sf.net/support/tracker.php?aid=1686495 1686495]&lt;br /&gt;
** Solutions:&lt;br /&gt;
*** make synfig installation relocatable and more robust&lt;br /&gt;
*** come up with a solution for the gtk stuff.&lt;br /&gt;
* fix the rest of the regressions, crashes, freezes and compile errors.&lt;br /&gt;
** Bugs: &lt;br /&gt;
** Solution: more debugging&lt;br /&gt;
* fixes for any of the open [[Bugs|bugs]].&lt;br /&gt;
* embedded source code documentation&lt;br /&gt;
* almost anything else&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Completed =&lt;br /&gt;
&lt;br /&gt;
Move releases here when they are done.&lt;br /&gt;
&lt;br /&gt;
== synfig 0.61.07 ==&lt;br /&gt;
&lt;br /&gt;
Crashes:&lt;br /&gt;
&lt;br /&gt;
* Fixed crash rendering http://dooglus.rincevent.net/synfig/crasher3.sif&lt;br /&gt;
* Fixed crash creating new paste canvas layers ([http://sf.net/support/tracker.php?aid=1356449 1356449])&lt;br /&gt;
* Fixed crash with relative pathnames ([http://sf.net/support/tracker.php?aid=1383736 1383736])&lt;br /&gt;
* Fixed disconnect bug [http://sf.net/support/tracker.php?aid=1356376 1356376] ...&lt;br /&gt;
Other:&lt;br /&gt;
&lt;br /&gt;
* Fixed importing images on amd64 ([http://sf.net/support/tracker.php?aid=1692825 1692825])&lt;br /&gt;
* Moved pixmaps to a subdir&lt;br /&gt;
&lt;br /&gt;
== synfig 0.61.06 ==&lt;br /&gt;
&lt;br /&gt;
* Fix the synfigstudio's icon finding and SYNFIG_ROOT stuff - [http://sf.net/support/tracker.php?aid=1568925 1568925]&lt;br /&gt;
* Fix the touchpad/mouse/Input Devices issue;  It's initially very off putting when you can't draw even a single circle - [http://sf.net/support/tracker.php?aid=1677510 1677510]&lt;br /&gt;
* Fix the uninstall in the Windows packages, and also make a single download available - [http://sf.net/support/tracker.php?aid=1673269 1673269]&lt;br /&gt;
* fix the synfig rendering targets that crash (gif, dv, ffmpeg, imagemagick).&amp;lt;br&amp;gt;Bugs: [http://sf.net/support/tracker.php?aid=1346746 1346746] [http://sf.net/support/tracker.php?aid=1480722 1480722] ...&lt;br /&gt;
* create better builds for Windows.&lt;br /&gt;
* fix miscompilation of synfig with g++ 4.1.x and g++ 4.2&amp;lt;br&amp;gt;Bugs: [http://sf.net/support/tracker.php?aid=1509627 1509627] [http://bugs.debian.org/375080 DEB375080]&lt;br /&gt;
* fix synfig OOM when rendering the synfigstudio images on non-intel platforms.&amp;lt;br&amp;gt;Bugs: [http://sf.net/support/tracker.php?aid=1497893 1497893] [http://bugs.debian.org/369646 DEB369646]&lt;br /&gt;
* fix synfigstudio so that the toolbox window is shown on the taskbar/panel when no image is open.&amp;lt;br&amp;gt;Bugs: [http://bugs.debian.org/366731 DEB366731]&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Dev:Wish_list&amp;diff=7181</id>
		<title>Dev:Wish list</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Dev:Wish_list&amp;diff=7181"/>
				<updated>2008-05-28T13:50:11Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Wishes */ motion blur effect&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''''Warning''''': We need more people working on the code if we are going to be able to achieve all the feature requests.&lt;br /&gt;
&lt;br /&gt;
Got a great idea for a new feature? Just add it here, or on the [http://sourceforge.net/tracker/?group_id=144022&amp;amp;atid=757419 feature requests tracker]. Before you do, please check the [http://svn.voria.com/code/ETL/trunk/TODO etl], [http://svn.voria.com/code/synfig-core/trunk/TODO synfig] and [http://svn.voria.com/code/synfig-studio/trunk/TODO synfigstudio] TODO files for similar ideas. Please add a rating of how essential this feature is to your workflow according to the following scale:&lt;br /&gt;
&lt;br /&gt;
#&amp;quot;Well, it might be nifty. To someone.&amp;quot;&lt;br /&gt;
#&amp;quot;I probably would make use this&amp;quot;&lt;br /&gt;
#&amp;quot;It's not essential, but I'd really like to have this at my disposal.&amp;quot;&lt;br /&gt;
#&amp;quot;Synfig would be soooo much better with this change&amp;quot;&lt;br /&gt;
#&amp;quot;I can't/won't use Synfig without it!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== Wishes ==&lt;br /&gt;
&lt;br /&gt;
===Movement blur effect===&lt;br /&gt;
To make the motion most realistic for movies, it should be possible to activate in the render dialog the option to smear the border of all objects, which move faster than a given value. For example, if a ball gets shot over the canvas/rendering-screen with speed over 50 px/frame it should have a blurry streak attached. This effect could be applied only at rendering time as an after-effect. --[[User:SvH|SvH]] 09:50, 28 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Morph sets===&lt;br /&gt;
This feature is similar to some other suggestions below, just with another way to approach. In animations are many movements, which can be put in some kind of library, to make use of at a later time. For example, movements to animate the key moments of a mouth, sampling syllables. For vector graphics, it should be possible to define some key points, which move just a small amount of space, to form another syllable. These syllables in this example, should be stored in a drop down list, to be able to select them for the key time on the timeline.&lt;br /&gt;
A morph-set for walking-left-to-right is different from a morph-set for a mounth, which has as options a,e,i,o,u,bah-disgust,happy-smile. The morph-set has to be stored as vector coordinates in a relative way(offset), e.g. X1=+212,+34;X2=-56,-23;X3=+3,-88;&lt;br /&gt;
&lt;br /&gt;
To make use of the morph-set for the mouth, you have to define first, which vector points in your drawn mouth, correspond to the key-points of your morph-set. X1, X2, X3, Xn&lt;br /&gt;
&lt;br /&gt;
--[[User:SvH|SvH]] 06:53, 27 May 2008 (EDT)&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
===Render time approximation===&lt;br /&gt;
Synfigstudio should get a button in the render dialog, which calculates the total render time for the actual settings (frames per second, length of the film, resolution, output format) It should testrender 1 picture, when the amount of total frames is below 1000. Over 1000 frames, it should testrender 10 pictures for more precise calculation.&lt;br /&gt;
&lt;br /&gt;
--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
===Smartrendering===&lt;br /&gt;
I have made 25,000 small png-pictures with my 800Mhz computer in about 45 minutes. Synfigstudio did calculate each single frame of it. Nothing changed in this picture, so it does only need to get written to disk for the amount of pictures, until the next change (animation) has an effect on the output picture. This should save time for bigger projects with thousands of pictures.&lt;br /&gt;
&lt;br /&gt;
--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)   &lt;br /&gt;
&lt;br /&gt;
=== get_color method in text and radial blur ===&lt;br /&gt;
&lt;br /&gt;
[5] Without get_color method distorion produces artifacts &lt;br /&gt;
[http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1831355&amp;amp;group_id=144022&amp;amp;atid=757416 bug  1831355]. So I would like to get this problem fixed before doing something else. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== Full functional of group dialog ===&lt;br /&gt;
&lt;br /&gt;
[5] Group dialog is broken now [http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1796833&amp;amp;group_id=144022&amp;amp;atid=757416 bug 1796833]. So we should get old features work right before making new one. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== import/export .swf files ===&lt;br /&gt;
&lt;br /&gt;
very important productivity feature&lt;br /&gt;
&lt;br /&gt;
=== import/export .svg frames sequence, and/or .svg animations ===&lt;br /&gt;
&lt;br /&gt;
very important productivity feature&lt;br /&gt;
&lt;br /&gt;
=== a realtime .sif synchronized text window ===&lt;br /&gt;
&lt;br /&gt;
just like the xml editor of Inkscape, or the html editor in Dreamweaver (this is hugelly useful for productivity)&lt;br /&gt;
&lt;br /&gt;
I thinks scripting API can be implement in this way. For example you make XML DOM like implementation for python which alows to change DOM tree from python code and see chenges in canvas. By this way you can implement import/export scripts. Automation scripts. And a lot of different things. Even synchronization of animation between blender and synfig. --[[User:AkhIL|AkhIL]] 23:10, 26 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== choosing colour from gimp/inkscape palettes ===&lt;br /&gt;
&lt;br /&gt;
very useful when you need some colour comformity of what you're doing &lt;br /&gt;
&lt;br /&gt;
=== Good high-level documentation of the source code ===&lt;br /&gt;
&lt;br /&gt;
(2) It'd be nice if a newbie could quickly navigate around the source code. The best thing to do would be to add top-level comments in each file, explaining what that file does, a README.TXT in each directory, explaining what's in that directory. This would be pretty fast and easy to do, and make it much easier for new programmers to join. &lt;br /&gt;
&lt;br /&gt;
Time permitting, it would also be good to document on a high level what the data structures are, but that's harder, since those tend to evolve, and it is often difficult to keep in sync. It would also be useful to document what individual functions do (just a one-liner high-level description), but that also takes more time.&lt;br /&gt;
: There is a page link in the wiki that connect to the [http://www.synfig.com/doc Synfig API Documentation]. I think this link should be highlighted to be more accessible for newbies contributors and mature developers (the link was found [[Releases/DeveloperPreview#Support | here]]). --[[User:Genete|Genete]] 10:02, 11 December 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Mathematical functions to animate ===&lt;br /&gt;
(2/4) If you want to make a waving flag, it would be handful a sine function, tuned with random correctors, for example. &lt;br /&gt;
: -This should generate waypoints each 1, 2, 4 frames or any other step at artist's wish.&lt;br /&gt;
: -When applying a function you can add it to current values, add it to 1st frame values or simply override old values. Perhaps other options (such multiplication) would be fine, too. Something like texture editor in [http://www.artofillusion.org Art of Illusion], perhaps.&lt;br /&gt;
Perhaps it would be useful reusing the [http://www.gnu.org/software/octave/ Octave] source code to parse mathematical expressions.&lt;br /&gt;
I have rated this wish with a '2' because undoubtly many users will not be familiar to mathematical concepts, but for those who will be, I'd rate it with a 4. It would be possible to make a ball describing a parabolic moving in no time.&lt;br /&gt;
[[User:ajotatxe|ajotatxe]] 20 November 2007&lt;br /&gt;
: dooglus can probably chime in better than I here (see his example of balls on mathematical paths at http://uk.youtube.com/watch?v=YTpSfUthuVE ), but I believe that this is already possible.  Synfig does support a variety of mathematical transforms for parameters, although the way you do this is by no means intuitive.  (You might also want to check out the preambletaffy.sifz example for an easier approach to a waving flag. I know you were just using that as an example, but for the record...) [[User:Pxegeek|Pxegeek]] 00:58, 21 November 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
: I'd also rate it with a (4) (and updated the rating accordingly), not for this special case, but to make many workarounds much easier.  Simulating [Parabolic Shot|free fall], for example, would be a lot easier with real formulas.  I don't know, though how easy it will be to implement, maybe waiting for a scripting interface to be implemented is better than hacking this feature in an ad-hoc manner.  --[[User:Rubikcube|Rubikcube]] 16:38, 29 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Warning about editing bizarre things in animate editing mode ===&lt;br /&gt;
(3.5) It seems to have little sense animate certain things like Blend Method or Type of Feather. It would be very nice that the program asked comfirmation if you change these attributes in animate editing mode. If you do want to, you would have three options: &amp;quot;Yes, never ask&amp;quot;, &amp;quot;Yes, never ask for this attribute&amp;quot;, &amp;quot;No&amp;quot;. I guess that internally, this attributes has integer type (or something like that) and the attributes that you normally want to animate, float type, so I think that this feature is relatively easy to implement. My English is not very good, so please feel free to fix this post.&lt;br /&gt;
[[User:ajotatxe|ajotatxe]] 20 November 2007&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bones with FK &amp;amp; IK + grouping of objects into folders ===&lt;br /&gt;
&lt;br /&gt;
(1) Bones cane move specific vector assigned to them or the bones can have envelopes that move the vectors within their field of influence, much Like Anime Studio/Moho does. It's quite a time saving process of animating. Objects created can be saved into separate groups or folders using the same system as Anime Studio/Moho -Shadowphoenix 27/8/2007&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Animated sketch ===&lt;br /&gt;
&lt;br /&gt;
(1) it would be great, if the tool Sketch was animatable (for example, in a form of a special sketch-layer). --Zelgadis 2007-06-14&lt;br /&gt;
&lt;br /&gt;
=== Duck for Amount value in Zoom layer ===&lt;br /&gt;
&lt;br /&gt;
(2) It would be nice if Amount value in Zoom layer was controlled by additional duck. --[[User:Zelgadis|Zelgadis]] 02:49, 29 December 2007 (EST)&lt;br /&gt;
: I found that I can better use Warp layer instead of Zoom to change size. But it'd be nice to have Amount duck for Zoom layer anyway...&lt;br /&gt;
:: The Amount parameter works exponentially; each time you add 1 to the Amount, the image is zoomed by a further factor of e (= 2.71828 or so).  Would a duck be any use if it just controlled the value of Amount in a linear way?&lt;br /&gt;
:: Workarounds include: export Amount, select it in the children dialog.  Whatever's selected in the children dialog shows a duck.  You can adjust it using that duck.&lt;br /&gt;
:: Also, if you use a Stretch layer, convert the Amount to Composite, export the X-Axis and connect it to the Y-Axis, then you have a duck-controllable fixed-aspect zoom. -- [[User:Dooglus|dooglus]] 15:32, 15 January 2008 (EST)&lt;br /&gt;
::: Yeah I found this workaround, but it's to much actions - i prefer better use Warp or Stretch layers. Why not the link Amount duck and Amount value with logarithmic function? ;) --[[User:Zelgadis|Zelgadis]] 10:33, 17 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatic colour palette optimisation ===&lt;br /&gt;
&lt;br /&gt;
(0) it would be nice to use libcontrast [http://david.navi.cx/blog/?p=132] [http://david.navi.cx/blog/?p=94] [http://david.navi.cx/blog/?p=99] [http://svn.gnome.org/svn/xchat-gnome/trunk/src/libcontrast/] to automatically adjust selected or all the palette items for best visual contrast. It would also be interesting to have a layer that uses this code to filter the image.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arbitrary Color Channels ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; The ability for the user to create any number of custom channels for various purposes.&lt;br /&gt;
&lt;br /&gt;
=== Autorecover History ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; It would be great if autorecover could also recover the associated history of a file in the event of a crash.&lt;br /&gt;
&lt;br /&gt;
=== Layer Convert ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;(4)&amp;lt;/strike&amp;gt; (2) &amp;amp;mdash; The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''&lt;br /&gt;
&lt;br /&gt;
=== Vector fill bucket ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[Region Layer|region layer]]). &amp;lt;p&amp;gt;Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;If this is implemented, it will probably be necessary to change the existing &amp;quot;fill&amp;quot; tool's name and icon to a &amp;quot;color injector&amp;quot; (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.&lt;br /&gt;
&lt;br /&gt;
*Inkscape has a very innvative version of this tool. Maybe you can just grab the code from there and integrate it in synfig? --[[User:SvH|SvH]] 01:37, 14 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== [[redraw tool]] ===&lt;br /&gt;
&lt;br /&gt;
(4-5) &amp;amp;mdash; Intutive reshaping of path-based layers. See link.&lt;br /&gt;
&lt;br /&gt;
=== [http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance] ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; This should solve all complaints about the layout, without requiring Synfig to be &amp;quot;just like program (x)&amp;quot;. See [[UI Reloaded]] for progress on this.&lt;br /&gt;
&lt;br /&gt;
=== Feedback for [[Smooth Move Tool]] ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; This tool does what a lot of folks are looking for, warping selected ducks in a &amp;quot;soft&amp;quot; fashion. But it's not very obvious what sort of effect it will have, from the tool's interface. It needs some sort of momentary center-of-action and radius indicator at the very least. Perhaps an &amp;quot;influence gradient&amp;quot; overlaid on the canvas once Synfig's core is sped up?&lt;br /&gt;
&lt;br /&gt;
=== Networkability ===&lt;br /&gt;
&lt;br /&gt;
(2) &amp;amp;mdash; Like Inkscape's &amp;quot;inkboard&amp;quot; feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option. This should probably farm off all the networking stuff to the telepathy framework so that synfig doesn't have to deal with all the account/etc issues.&lt;br /&gt;
&lt;br /&gt;
=== Intuitive tangent modification ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.&lt;br /&gt;
&lt;br /&gt;
-Agreed; blender does this with its IPO curves, and it's a really efficient way to work.&lt;br /&gt;
&lt;br /&gt;
=== Plugin API ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
=== Python support ===&lt;br /&gt;
&lt;br /&gt;
(1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.&lt;br /&gt;
&lt;br /&gt;
I suuose to join this request with [[Wish_list#a_realtime_.sif_synchronized_text_window]]. We can implement python access to XML DOM and write XML Editor in python. --[[User:AkhIL|AkhIL]] 06:54, 30 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== mod_synfig ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; For Apache. Render .sif to some format like png/mng on access.&lt;br /&gt;
&lt;br /&gt;
=== synfig nsplugin ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; Let Mozilla and Mozilla-based view synfig files in-browser.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Align function ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; Align objects at a common border (as in Inkscape)&lt;br /&gt;
&lt;br /&gt;
=== Improved SVG import ===&lt;br /&gt;
&lt;br /&gt;
(4) &amp;amp;mdash; Currently, all importing an SVG does is render it in ImageMagick. What I want is the ability to import the SVG document so that all the shapes, etc. of the SVG document show up as their equivilant synfig layers - i.e. if I had put them there myself. I'm trying to write a patch for this but the codebase is mostly undocumented. [[User:KMeist|KMeist]] 16:38, 25 Feb 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
[[svg2synfig]] could be incorporated using an open source XSLT processor. --[[User:Dmd|Dmd]] 13:34, 26 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Gradient Paint Tool ===&lt;br /&gt;
&lt;br /&gt;
How about a tool that can 'paint' a gradient object.  For example the options would be width and gradient type, one would make a stroke with the tool and the gradient would be automatically applied inside of the outline (set by width).  This would save the trouble of having to the all the encapsulation stuff. (Actually any tool that makes creating gradient one step would be good).--[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bone Animation Tools ===&lt;br /&gt;
&lt;br /&gt;
Bone system with inverse kinematics, very important for quick animation. You put bones on a drawed man and you can animate him like a puppet. I'm using that in Moho (lost marble product).--[[User:Ziolive|ziolive]] 23 Aug 2006&lt;br /&gt;
*I would find this very useful too. I think it is called '''rigging'''(4/5) --[[User:SvH|SvH]] 01:33, 14 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== AVI Backgrounds ===&lt;br /&gt;
Is there any way I can add an avi as a background so I could add facial expressions to a stop-motion animated figure. [zotz here, I was thinking DV background or extra timeline. I would like to mix animations with live footage. rating (3/4)]&lt;br /&gt;
&lt;br /&gt;
=== Character tool on Tool Options Dialog ===&lt;br /&gt;
&lt;br /&gt;
I want to use the as a character generator for a TV show. By using chroma key hide the background.  Even better interface to a video overlay card with Alpha blending.&lt;br /&gt;
&lt;br /&gt;
=== Collect for Publication ===&lt;br /&gt;
&lt;br /&gt;
(3/4) - (zotz) Menu item, functionality that would collect alll files referenced in a sif and place them all in a tgz for sending elsewhere or publishing anumations in source form.&lt;br /&gt;
&lt;br /&gt;
=== Object Library ===&lt;br /&gt;
&lt;br /&gt;
(3/4) - (zotz) Haven't thought this all through yet, but synfig could come with a library of categotrised &amp;quot;objects&amp;quot; with a copyleft license (GPL?  CC BY-SA?) An animation clip art type deal.&lt;br /&gt;
**I'd suggest this should be public domain and distributed by openclipart.org -- --[[User:PaulWise|pabs]]&lt;br /&gt;
&lt;br /&gt;
=== Flash Export ===&lt;br /&gt;
&lt;br /&gt;
(3/4) Well, might just be me but if there was a posiblity to  export in .swf or .fla, I think the project might become a lot more popular.[[User:Conceit|Conceit]]&lt;br /&gt;
&lt;br /&gt;
(4/5) I wholeheartedly agree. I would definitely use synfig more if this feature were added and it would most definitely increase popularity. [[User:cdj05a|cdj05a]]&lt;br /&gt;
&lt;br /&gt;
=== Single window ===&lt;br /&gt;
&lt;br /&gt;
Depending on individual desktop setups, single window is sometimes preferable to many  windows. Can we have a single-window option?&lt;br /&gt;
&lt;br /&gt;
Also, even with many windows, Windows-users especially might find it better if all the windows only appeared as a single one on the taskbar.&lt;br /&gt;
&lt;br /&gt;
=== Line width tool ===&lt;br /&gt;
(4) It will be good to have a tool for easy changing line width. There was a such tool in earlier versions, but it's not usable. I'm often use variable line width, when drawing in synfig, so it is important for me. -- [[User:Zelgadis|Zelgadis]] 2007-09-09&lt;br /&gt;
&lt;br /&gt;
: It is [[FAQ#Where did the polygon, draw, sketch, and width tools go?|still available]].  Also, you can turn on the width ducks, using Alt-5. -- [[User:Dooglus|dooglus]] 12:18, 9 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
:: It is available, but I never was able to figure out how it works. Alt-5 works, but it is hard to set width to zero, for example. -- [[User:Zelgadis|Zelgadis]] 2007-09-10&lt;br /&gt;
&lt;br /&gt;
::: Are you wanting something that works on one vertex at a time?  Or all the vertices in an area?  Apparently the width tool was designed to work on a bunch of vertices at once.  I didn't figure out how it works though, either. -- [[User:Dooglus|dooglus]] 16:57, 10 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
:::: Width tool is surely a mystery. :) I'm waiting for something that works on one vertex at time. I liked the way as width was changed in Moho (Anime Studio now) - there was a special width tool and holding left mouse button on the vertex and moving cursor left decreasing width value, moving right - increasing. Maybe it make sense to rework Width tool in such way. -- [[User:Zelgadis|Zelgadis]] 2007-09-13&lt;br /&gt;
&lt;br /&gt;
=== Export Wizard ===&lt;br /&gt;
&lt;br /&gt;
(2/4) Conversion and export to other file formats (mpg, avi, flash formats, others, and the synfig format) with a step by step wizard for choosing format and place of saving. Similar to Gimp's saving of .png files but for movie/video type files. --&lt;br /&gt;
[[User:Hiddenghost|hiddenghost]]&lt;br /&gt;
&lt;br /&gt;
=== Using Synfig as a portable app ===&lt;br /&gt;
&lt;br /&gt;
(3) This isn't really a feature request (though it could be) but I was wondering if synfig could be used as a portable application (as in www.portableapps.com). Does the windows install require registry access? i really want to use Synfig at work, but I'm reluctant to install it just in case it leave footprints in the regisitry or something, and it would be sweet to use it on my travels as well. Only thing is, I can't test it out at home because I am using Linux.&lt;br /&gt;
See also: http://portableapps.com/node/5761&lt;br /&gt;
[[User:Zenoscope|zenoscope]]&lt;br /&gt;
&lt;br /&gt;
This isn't currently possible without modifying the source code. That has been on my TODO list for ages [[User:PaulWise|pabs]] 01:17, 26 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Allow organize child valuenodes in an hierarchy ===&lt;br /&gt;
(3-2) And allow maintain the organization once the file is saved. At the moment they are reordered in alphabetical order which is useless and annoying.&lt;br /&gt;
&lt;br /&gt;
=== Triangle sliders to be always visible ===&lt;br /&gt;
(3) I would like that the triangle sliders from [[Colors Dialog]] and [[Gradient Editor Dialog]] were visible whatever color or channel you're editing. Some times when the color or channel is to bright or light the slider is difficult to distinguish. --[[User:Genete|Genete]] 14:30, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== XICC support ===&lt;br /&gt;
&lt;br /&gt;
It would be cool if synfigstudio had support for [http://burtonini.com/blog/computers/xicc XICC].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Area to Edit ===&lt;br /&gt;
&lt;br /&gt;
An option like blender - select area to update would be nice, so the only part of the image that updates when you add or change something is in the selected area&lt;br /&gt;
&lt;br /&gt;
ie. when working on a complex composition, studio doesn't know, when I tweak a tiny part of the composition, that only that part needs redrawing, so it redraws the whole thing.  It would be good if there was some way of telling it which part to focus on. -- [[User:Dooglus|dooglus]] 04:02, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Histograms ===&lt;br /&gt;
&lt;br /&gt;
 01:23  * AkhIL wish to have histograms and luma/color scope like [http://mac.softpedia.com/progScreenshots/Avid-Xpress-DV-Screenshot-14207.html] in synfig&lt;br /&gt;
&lt;br /&gt;
I've looked at those pictures but don't know what they're showing.  Can you describe what those scopes are doing, and what the histograms display?  ie. what are the X and Y axes of the histograms? -- [[User:Dooglus|dooglus]] 04:07, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
First look this description in blender wiki [http://wiki.blender.org/index.php/Manual/VSE_Modes]&lt;br /&gt;
&lt;br /&gt;
Ok There is four things.&lt;br /&gt;
* Upper left is Lumascope (Luma Waveform in blender). X-Axis represents image's X-Axys. Y-Axis  is average luminescence of column of pixels.&lt;br /&gt;
* Upper right is Chromascope (Chroma Vectorscope in blender). Just look description on blender wiki.&lt;br /&gt;
* Lower left is like Lumascope but for each channel &lt;br /&gt;
* Lower right is histograms. X is luminescence and Y is count of pixels with such luminiscence.&lt;br /&gt;
&lt;br /&gt;
=== Sound Layer ===&lt;br /&gt;
&lt;br /&gt;
(4) It would be a very good improvement if the sound system were implemented into synfig in [[Sound Layer | this]] way. --[[User:Genete|Genete]] 07:46, 8 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Rearrange the view of waypoints for Canvas param ===&lt;br /&gt;
As reported in [http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1888858&amp;amp;group_id=144022&amp;amp;atid=757416 Bug #1888858] waypoints are not displayed for canvas switch events.&lt;br /&gt;
I suggest to rearrange waypoints display according to [[Media:Canvas_prop.png|this scheme]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Width weigths ===&lt;br /&gt;
Is it possible to add &amp;quot;weigths&amp;quot; for widths? ^_^ I.e. width changes not all the way along the segment. Maybe something like a duck on bline which indicates the region where the width of current vertex isn't changed.&lt;br /&gt;
[[Media:width-proposal.png|Illustration here.]]&lt;br /&gt;
&lt;br /&gt;
More ideas around this concept in [http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-04-16.log this conversation]. Although the log of that day is very interesting the lines related to this idea are from 22:38 to 23:43. [[User:Genete|Genete]] 17:51, 16 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Improved Colour Dialog ===&lt;br /&gt;
How easy is it to stick in a colour square/wheel? Messing with sliders is somewhat obstructive.&lt;br /&gt;
&lt;br /&gt;
=== Insert Waypoints ===&lt;br /&gt;
A button to create a waypoint for every selected duck, in its current position. Moving each duck up a bit and down again quickly gets tedious.&lt;br /&gt;
:If the duck in question has already a waypoint then you don't need to move it to create a new waypoint. Just select the corresponding parameter in your child list panel and select 'Add Waypoint' from the right click context menu over the parameter. No need to have the duck selected. If you want to freeze the entire bline just do that over the Bline Point List. [[User:Genete|Genete]] 07:48, 29 April 2008 (EDT)&lt;br /&gt;
::Yes, but it would be nice to have opportunity to add waypoint to parameer which not have any ducks yet (i.e. non-animated parameter). --[[User:Zelgadis|Zelgadis]] 08:33, 29 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatically split tangeants ===&lt;br /&gt;
&lt;br /&gt;
Holding shift while moving tangeant ducks should automatically split them. They can be rejoined if necessary through the context menu as they are now.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Dev:Wish_list&amp;diff=7180</id>
		<title>Dev:Wish list</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Dev:Wish_list&amp;diff=7180"/>
				<updated>2008-05-27T10:53:53Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Wishes */ Morph-set&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''''Warning''''': We need more people working on the code if we are going to be able to achieve all the feature requests.&lt;br /&gt;
&lt;br /&gt;
Got a great idea for a new feature? Just add it here, or on the [http://sourceforge.net/tracker/?group_id=144022&amp;amp;atid=757419 feature requests tracker]. Before you do, please check the [http://svn.voria.com/code/ETL/trunk/TODO etl], [http://svn.voria.com/code/synfig-core/trunk/TODO synfig] and [http://svn.voria.com/code/synfig-studio/trunk/TODO synfigstudio] TODO files for similar ideas. Please add a rating of how essential this feature is to your workflow according to the following scale:&lt;br /&gt;
&lt;br /&gt;
#&amp;quot;Well, it might be nifty. To someone.&amp;quot;&lt;br /&gt;
#&amp;quot;I probably would make use this&amp;quot;&lt;br /&gt;
#&amp;quot;It's not essential, but I'd really like to have this at my disposal.&amp;quot;&lt;br /&gt;
#&amp;quot;Synfig would be soooo much better with this change&amp;quot;&lt;br /&gt;
#&amp;quot;I can't/won't use Synfig without it!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== Wishes ==&lt;br /&gt;
&lt;br /&gt;
===Morph sets===&lt;br /&gt;
This feature is similar to some other suggestions below, just with another way to approach. In animations are many movements, which can be put in some kind of library, to make use of at a later time. For example, movements to animate the key moments of a mouth, sampling syllables. For vector graphics, it should be possible to define some key points, which move just a small amount of space, to form another syllable. These syllables in this example, should be stored in a drop down list, to be able to select them for the key time on the timeline.&lt;br /&gt;
A morph-set for walking-left-to-right is different from a morph-set for a mounth, which has as options a,e,i,o,u,bah-disgust,happy-smile. The morph-set has to be stored as vector coordinates in a relative way(offset), e.g. X1=+212,+34;X2=-56,-23;X3=+3,-88;&lt;br /&gt;
&lt;br /&gt;
To make use of the morph-set for the mouth, you have to define first, which vector points in your drawn mouth, correspond to the key-points of your morph-set. X1, X2, X3, Xn&lt;br /&gt;
&lt;br /&gt;
--[[User:SvH|SvH]] 06:53, 27 May 2008 (EDT)&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
===Render time approximation===&lt;br /&gt;
Synfigstudio should get a button in the render dialog, which calculates the total render time for the actual settings (frames per second, length of the film, resolution, output format) It should testrender 1 picture, when the amount of total frames is below 1000. Over 1000 frames, it should testrender 10 pictures for more precise calculation.&lt;br /&gt;
&lt;br /&gt;
--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
===Smartrendering===&lt;br /&gt;
I have made 25,000 small png-pictures with my 800Mhz computer in about 45 minutes. Synfigstudio did calculate each single frame of it. Nothing changed in this picture, so it does only need to get written to disk for the amount of pictures, until the next change (animation) has an effect on the output picture. This should save time for bigger projects with thousands of pictures.&lt;br /&gt;
&lt;br /&gt;
--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)   &lt;br /&gt;
&lt;br /&gt;
=== get_color method in text and radial blur ===&lt;br /&gt;
&lt;br /&gt;
[5] Without get_color method distorion produces artifacts &lt;br /&gt;
[http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1831355&amp;amp;group_id=144022&amp;amp;atid=757416 bug  1831355]. So I would like to get this problem fixed before doing something else. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== Full functional of group dialog ===&lt;br /&gt;
&lt;br /&gt;
[5] Group dialog is broken now [http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1796833&amp;amp;group_id=144022&amp;amp;atid=757416 bug 1796833]. So we should get old features work right before making new one. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== import/export .swf files ===&lt;br /&gt;
&lt;br /&gt;
very important productivity feature&lt;br /&gt;
&lt;br /&gt;
=== import/export .svg frames sequence, and/or .svg animations ===&lt;br /&gt;
&lt;br /&gt;
very important productivity feature&lt;br /&gt;
&lt;br /&gt;
=== a realtime .sif synchronized text window ===&lt;br /&gt;
&lt;br /&gt;
just like the xml editor of Inkscape, or the html editor in Dreamweaver (this is hugelly useful for productivity)&lt;br /&gt;
&lt;br /&gt;
I thinks scripting API can be implement in this way. For example you make XML DOM like implementation for python which alows to change DOM tree from python code and see chenges in canvas. By this way you can implement import/export scripts. Automation scripts. And a lot of different things. Even synchronization of animation between blender and synfig. --[[User:AkhIL|AkhIL]] 23:10, 26 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== choosing colour from gimp/inkscape palettes ===&lt;br /&gt;
&lt;br /&gt;
very useful when you need some colour comformity of what you're doing &lt;br /&gt;
&lt;br /&gt;
=== Good high-level documentation of the source code ===&lt;br /&gt;
&lt;br /&gt;
(2) It'd be nice if a newbie could quickly navigate around the source code. The best thing to do would be to add top-level comments in each file, explaining what that file does, a README.TXT in each directory, explaining what's in that directory. This would be pretty fast and easy to do, and make it much easier for new programmers to join. &lt;br /&gt;
&lt;br /&gt;
Time permitting, it would also be good to document on a high level what the data structures are, but that's harder, since those tend to evolve, and it is often difficult to keep in sync. It would also be useful to document what individual functions do (just a one-liner high-level description), but that also takes more time.&lt;br /&gt;
: There is a page link in the wiki that connect to the [http://www.synfig.com/doc Synfig API Documentation]. I think this link should be highlighted to be more accessible for newbies contributors and mature developers (the link was found [[Releases/DeveloperPreview#Support | here]]). --[[User:Genete|Genete]] 10:02, 11 December 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Mathematical functions to animate ===&lt;br /&gt;
(2/4) If you want to make a waving flag, it would be handful a sine function, tuned with random correctors, for example. &lt;br /&gt;
: -This should generate waypoints each 1, 2, 4 frames or any other step at artist's wish.&lt;br /&gt;
: -When applying a function you can add it to current values, add it to 1st frame values or simply override old values. Perhaps other options (such multiplication) would be fine, too. Something like texture editor in [http://www.artofillusion.org Art of Illusion], perhaps.&lt;br /&gt;
Perhaps it would be useful reusing the [http://www.gnu.org/software/octave/ Octave] source code to parse mathematical expressions.&lt;br /&gt;
I have rated this wish with a '2' because undoubtly many users will not be familiar to mathematical concepts, but for those who will be, I'd rate it with a 4. It would be possible to make a ball describing a parabolic moving in no time.&lt;br /&gt;
[[User:ajotatxe|ajotatxe]] 20 November 2007&lt;br /&gt;
: dooglus can probably chime in better than I here (see his example of balls on mathematical paths at http://uk.youtube.com/watch?v=YTpSfUthuVE ), but I believe that this is already possible.  Synfig does support a variety of mathematical transforms for parameters, although the way you do this is by no means intuitive.  (You might also want to check out the preambletaffy.sifz example for an easier approach to a waving flag. I know you were just using that as an example, but for the record...) [[User:Pxegeek|Pxegeek]] 00:58, 21 November 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
: I'd also rate it with a (4) (and updated the rating accordingly), not for this special case, but to make many workarounds much easier.  Simulating [Parabolic Shot|free fall], for example, would be a lot easier with real formulas.  I don't know, though how easy it will be to implement, maybe waiting for a scripting interface to be implemented is better than hacking this feature in an ad-hoc manner.  --[[User:Rubikcube|Rubikcube]] 16:38, 29 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Warning about editing bizarre things in animate editing mode ===&lt;br /&gt;
(3.5) It seems to have little sense animate certain things like Blend Method or Type of Feather. It would be very nice that the program asked comfirmation if you change these attributes in animate editing mode. If you do want to, you would have three options: &amp;quot;Yes, never ask&amp;quot;, &amp;quot;Yes, never ask for this attribute&amp;quot;, &amp;quot;No&amp;quot;. I guess that internally, this attributes has integer type (or something like that) and the attributes that you normally want to animate, float type, so I think that this feature is relatively easy to implement. My English is not very good, so please feel free to fix this post.&lt;br /&gt;
[[User:ajotatxe|ajotatxe]] 20 November 2007&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bones with FK &amp;amp; IK + grouping of objects into folders ===&lt;br /&gt;
&lt;br /&gt;
(1) Bones cane move specific vector assigned to them or the bones can have envelopes that move the vectors within their field of influence, much Like Anime Studio/Moho does. It's quite a time saving process of animating. Objects created can be saved into separate groups or folders using the same system as Anime Studio/Moho -Shadowphoenix 27/8/2007&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Animated sketch ===&lt;br /&gt;
&lt;br /&gt;
(1) it would be great, if the tool Sketch was animatable (for example, in a form of a special sketch-layer). --Zelgadis 2007-06-14&lt;br /&gt;
&lt;br /&gt;
=== Duck for Amount value in Zoom layer ===&lt;br /&gt;
&lt;br /&gt;
(2) It would be nice if Amount value in Zoom layer was controlled by additional duck. --[[User:Zelgadis|Zelgadis]] 02:49, 29 December 2007 (EST)&lt;br /&gt;
: I found that I can better use Warp layer instead of Zoom to change size. But it'd be nice to have Amount duck for Zoom layer anyway...&lt;br /&gt;
:: The Amount parameter works exponentially; each time you add 1 to the Amount, the image is zoomed by a further factor of e (= 2.71828 or so).  Would a duck be any use if it just controlled the value of Amount in a linear way?&lt;br /&gt;
:: Workarounds include: export Amount, select it in the children dialog.  Whatever's selected in the children dialog shows a duck.  You can adjust it using that duck.&lt;br /&gt;
:: Also, if you use a Stretch layer, convert the Amount to Composite, export the X-Axis and connect it to the Y-Axis, then you have a duck-controllable fixed-aspect zoom. -- [[User:Dooglus|dooglus]] 15:32, 15 January 2008 (EST)&lt;br /&gt;
::: Yeah I found this workaround, but it's to much actions - i prefer better use Warp or Stretch layers. Why not the link Amount duck and Amount value with logarithmic function? ;) --[[User:Zelgadis|Zelgadis]] 10:33, 17 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatic colour palette optimisation ===&lt;br /&gt;
&lt;br /&gt;
(0) it would be nice to use libcontrast [http://david.navi.cx/blog/?p=132] [http://david.navi.cx/blog/?p=94] [http://david.navi.cx/blog/?p=99] [http://svn.gnome.org/svn/xchat-gnome/trunk/src/libcontrast/] to automatically adjust selected or all the palette items for best visual contrast. It would also be interesting to have a layer that uses this code to filter the image.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arbitrary Color Channels ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; The ability for the user to create any number of custom channels for various purposes.&lt;br /&gt;
&lt;br /&gt;
=== Autorecover History ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; It would be great if autorecover could also recover the associated history of a file in the event of a crash.&lt;br /&gt;
&lt;br /&gt;
=== Layer Convert ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;(4)&amp;lt;/strike&amp;gt; (2) &amp;amp;mdash; The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''&lt;br /&gt;
&lt;br /&gt;
=== Vector fill bucket ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[Region Layer|region layer]]). &amp;lt;p&amp;gt;Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;If this is implemented, it will probably be necessary to change the existing &amp;quot;fill&amp;quot; tool's name and icon to a &amp;quot;color injector&amp;quot; (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.&lt;br /&gt;
&lt;br /&gt;
*Inkscape has a very innvative version of this tool. Maybe you can just grab the code from there and integrate it in synfig? --[[User:SvH|SvH]] 01:37, 14 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== [[redraw tool]] ===&lt;br /&gt;
&lt;br /&gt;
(4-5) &amp;amp;mdash; Intutive reshaping of path-based layers. See link.&lt;br /&gt;
&lt;br /&gt;
=== [http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance] ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; This should solve all complaints about the layout, without requiring Synfig to be &amp;quot;just like program (x)&amp;quot;. See [[UI Reloaded]] for progress on this.&lt;br /&gt;
&lt;br /&gt;
=== Feedback for [[Smooth Move Tool]] ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; This tool does what a lot of folks are looking for, warping selected ducks in a &amp;quot;soft&amp;quot; fashion. But it's not very obvious what sort of effect it will have, from the tool's interface. It needs some sort of momentary center-of-action and radius indicator at the very least. Perhaps an &amp;quot;influence gradient&amp;quot; overlaid on the canvas once Synfig's core is sped up?&lt;br /&gt;
&lt;br /&gt;
=== Networkability ===&lt;br /&gt;
&lt;br /&gt;
(2) &amp;amp;mdash; Like Inkscape's &amp;quot;inkboard&amp;quot; feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option. This should probably farm off all the networking stuff to the telepathy framework so that synfig doesn't have to deal with all the account/etc issues.&lt;br /&gt;
&lt;br /&gt;
=== Intuitive tangent modification ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.&lt;br /&gt;
&lt;br /&gt;
-Agreed; blender does this with its IPO curves, and it's a really efficient way to work.&lt;br /&gt;
&lt;br /&gt;
=== Plugin API ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
=== Python support ===&lt;br /&gt;
&lt;br /&gt;
(1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.&lt;br /&gt;
&lt;br /&gt;
I suuose to join this request with [[Wish_list#a_realtime_.sif_synchronized_text_window]]. We can implement python access to XML DOM and write XML Editor in python. --[[User:AkhIL|AkhIL]] 06:54, 30 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== mod_synfig ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; For Apache. Render .sif to some format like png/mng on access.&lt;br /&gt;
&lt;br /&gt;
=== synfig nsplugin ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; Let Mozilla and Mozilla-based view synfig files in-browser.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Align function ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; Align objects at a common border (as in Inkscape)&lt;br /&gt;
&lt;br /&gt;
=== Improved SVG import ===&lt;br /&gt;
&lt;br /&gt;
(4) &amp;amp;mdash; Currently, all importing an SVG does is render it in ImageMagick. What I want is the ability to import the SVG document so that all the shapes, etc. of the SVG document show up as their equivilant synfig layers - i.e. if I had put them there myself. I'm trying to write a patch for this but the codebase is mostly undocumented. [[User:KMeist|KMeist]] 16:38, 25 Feb 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
[[svg2synfig]] could be incorporated using an open source XSLT processor. --[[User:Dmd|Dmd]] 13:34, 26 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Gradient Paint Tool ===&lt;br /&gt;
&lt;br /&gt;
How about a tool that can 'paint' a gradient object.  For example the options would be width and gradient type, one would make a stroke with the tool and the gradient would be automatically applied inside of the outline (set by width).  This would save the trouble of having to the all the encapsulation stuff. (Actually any tool that makes creating gradient one step would be good).--[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bone Animation Tools ===&lt;br /&gt;
&lt;br /&gt;
Bone system with inverse kinematics, very important for quick animation. You put bones on a drawed man and you can animate him like a puppet. I'm using that in Moho (lost marble product).--[[User:Ziolive|ziolive]] 23 Aug 2006&lt;br /&gt;
*I would find this very useful too. I think it is called '''rigging'''(4/5) --[[User:SvH|SvH]] 01:33, 14 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== AVI Backgrounds ===&lt;br /&gt;
Is there any way I can add an avi as a background so I could add facial expressions to a stop-motion animated figure. [zotz here, I was thinking DV background or extra timeline. I would like to mix animations with live footage. rating (3/4)]&lt;br /&gt;
&lt;br /&gt;
=== Character tool on Tool Options Dialog ===&lt;br /&gt;
&lt;br /&gt;
I want to use the as a character generator for a TV show. By using chroma key hide the background.  Even better interface to a video overlay card with Alpha blending.&lt;br /&gt;
&lt;br /&gt;
=== Collect for Publication ===&lt;br /&gt;
&lt;br /&gt;
(3/4) - (zotz) Menu item, functionality that would collect alll files referenced in a sif and place them all in a tgz for sending elsewhere or publishing anumations in source form.&lt;br /&gt;
&lt;br /&gt;
=== Object Library ===&lt;br /&gt;
&lt;br /&gt;
(3/4) - (zotz) Haven't thought this all through yet, but synfig could come with a library of categotrised &amp;quot;objects&amp;quot; with a copyleft license (GPL?  CC BY-SA?) An animation clip art type deal.&lt;br /&gt;
**I'd suggest this should be public domain and distributed by openclipart.org -- --[[User:PaulWise|pabs]]&lt;br /&gt;
&lt;br /&gt;
=== Flash Export ===&lt;br /&gt;
&lt;br /&gt;
(3/4) Well, might just be me but if there was a posiblity to  export in .swf or .fla, I think the project might become a lot more popular.[[User:Conceit|Conceit]]&lt;br /&gt;
&lt;br /&gt;
(4/5) I wholeheartedly agree. I would definitely use synfig more if this feature were added and it would most definitely increase popularity. [[User:cdj05a|cdj05a]]&lt;br /&gt;
&lt;br /&gt;
=== Single window ===&lt;br /&gt;
&lt;br /&gt;
Depending on individual desktop setups, single window is sometimes preferable to many  windows. Can we have a single-window option?&lt;br /&gt;
&lt;br /&gt;
Also, even with many windows, Windows-users especially might find it better if all the windows only appeared as a single one on the taskbar.&lt;br /&gt;
&lt;br /&gt;
=== Line width tool ===&lt;br /&gt;
(4) It will be good to have a tool for easy changing line width. There was a such tool in earlier versions, but it's not usable. I'm often use variable line width, when drawing in synfig, so it is important for me. -- [[User:Zelgadis|Zelgadis]] 2007-09-09&lt;br /&gt;
&lt;br /&gt;
: It is [[FAQ#Where did the polygon, draw, sketch, and width tools go?|still available]].  Also, you can turn on the width ducks, using Alt-5. -- [[User:Dooglus|dooglus]] 12:18, 9 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
:: It is available, but I never was able to figure out how it works. Alt-5 works, but it is hard to set width to zero, for example. -- [[User:Zelgadis|Zelgadis]] 2007-09-10&lt;br /&gt;
&lt;br /&gt;
::: Are you wanting something that works on one vertex at a time?  Or all the vertices in an area?  Apparently the width tool was designed to work on a bunch of vertices at once.  I didn't figure out how it works though, either. -- [[User:Dooglus|dooglus]] 16:57, 10 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
:::: Width tool is surely a mystery. :) I'm waiting for something that works on one vertex at time. I liked the way as width was changed in Moho (Anime Studio now) - there was a special width tool and holding left mouse button on the vertex and moving cursor left decreasing width value, moving right - increasing. Maybe it make sense to rework Width tool in such way. -- [[User:Zelgadis|Zelgadis]] 2007-09-13&lt;br /&gt;
&lt;br /&gt;
=== Export Wizard ===&lt;br /&gt;
&lt;br /&gt;
(2/4) Conversion and export to other file formats (mpg, avi, flash formats, others, and the synfig format) with a step by step wizard for choosing format and place of saving. Similar to Gimp's saving of .png files but for movie/video type files. --&lt;br /&gt;
[[User:Hiddenghost|hiddenghost]]&lt;br /&gt;
&lt;br /&gt;
=== Using Synfig as a portable app ===&lt;br /&gt;
&lt;br /&gt;
(3) This isn't really a feature request (though it could be) but I was wondering if synfig could be used as a portable application (as in www.portableapps.com). Does the windows install require registry access? i really want to use Synfig at work, but I'm reluctant to install it just in case it leave footprints in the regisitry or something, and it would be sweet to use it on my travels as well. Only thing is, I can't test it out at home because I am using Linux.&lt;br /&gt;
See also: http://portableapps.com/node/5761&lt;br /&gt;
[[User:Zenoscope|zenoscope]]&lt;br /&gt;
&lt;br /&gt;
This isn't currently possible without modifying the source code. That has been on my TODO list for ages [[User:PaulWise|pabs]] 01:17, 26 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Allow organize child valuenodes in an hierarchy ===&lt;br /&gt;
(3-2) And allow maintain the organization once the file is saved. At the moment they are reordered in alphabetical order which is useless and annoying.&lt;br /&gt;
&lt;br /&gt;
=== Triangle sliders to be always visible ===&lt;br /&gt;
(3) I would like that the triangle sliders from [[Colors Dialog]] and [[Gradient Editor Dialog]] were visible whatever color or channel you're editing. Some times when the color or channel is to bright or light the slider is difficult to distinguish. --[[User:Genete|Genete]] 14:30, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== XICC support ===&lt;br /&gt;
&lt;br /&gt;
It would be cool if synfigstudio had support for [http://burtonini.com/blog/computers/xicc XICC].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Area to Edit ===&lt;br /&gt;
&lt;br /&gt;
An option like blender - select area to update would be nice, so the only part of the image that updates when you add or change something is in the selected area&lt;br /&gt;
&lt;br /&gt;
ie. when working on a complex composition, studio doesn't know, when I tweak a tiny part of the composition, that only that part needs redrawing, so it redraws the whole thing.  It would be good if there was some way of telling it which part to focus on. -- [[User:Dooglus|dooglus]] 04:02, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Histograms ===&lt;br /&gt;
&lt;br /&gt;
 01:23  * AkhIL wish to have histograms and luma/color scope like [http://mac.softpedia.com/progScreenshots/Avid-Xpress-DV-Screenshot-14207.html] in synfig&lt;br /&gt;
&lt;br /&gt;
I've looked at those pictures but don't know what they're showing.  Can you describe what those scopes are doing, and what the histograms display?  ie. what are the X and Y axes of the histograms? -- [[User:Dooglus|dooglus]] 04:07, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
First look this description in blender wiki [http://wiki.blender.org/index.php/Manual/VSE_Modes]&lt;br /&gt;
&lt;br /&gt;
Ok There is four things.&lt;br /&gt;
* Upper left is Lumascope (Luma Waveform in blender). X-Axis represents image's X-Axys. Y-Axis  is average luminescence of column of pixels.&lt;br /&gt;
* Upper right is Chromascope (Chroma Vectorscope in blender). Just look description on blender wiki.&lt;br /&gt;
* Lower left is like Lumascope but for each channel &lt;br /&gt;
* Lower right is histograms. X is luminescence and Y is count of pixels with such luminiscence.&lt;br /&gt;
&lt;br /&gt;
=== Sound Layer ===&lt;br /&gt;
&lt;br /&gt;
(4) It would be a very good improvement if the sound system were implemented into synfig in [[Sound Layer | this]] way. --[[User:Genete|Genete]] 07:46, 8 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Rearrange the view of waypoints for Canvas param ===&lt;br /&gt;
As reported in [http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1888858&amp;amp;group_id=144022&amp;amp;atid=757416 Bug #1888858] waypoints are not displayed for canvas switch events.&lt;br /&gt;
I suggest to rearrange waypoints display according to [[Media:Canvas_prop.png|this scheme]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Width weigths ===&lt;br /&gt;
Is it possible to add &amp;quot;weigths&amp;quot; for widths? ^_^ I.e. width changes not all the way along the segment. Maybe something like a duck on bline which indicates the region where the width of current vertex isn't changed.&lt;br /&gt;
[[Media:width-proposal.png|Illustration here.]]&lt;br /&gt;
&lt;br /&gt;
More ideas around this concept in [http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-04-16.log this conversation]. Although the log of that day is very interesting the lines related to this idea are from 22:38 to 23:43. [[User:Genete|Genete]] 17:51, 16 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Improved Colour Dialog ===&lt;br /&gt;
How easy is it to stick in a colour square/wheel? Messing with sliders is somewhat obstructive.&lt;br /&gt;
&lt;br /&gt;
=== Insert Waypoints ===&lt;br /&gt;
A button to create a waypoint for every selected duck, in its current position. Moving each duck up a bit and down again quickly gets tedious.&lt;br /&gt;
:If the duck in question has already a waypoint then you don't need to move it to create a new waypoint. Just select the corresponding parameter in your child list panel and select 'Add Waypoint' from the right click context menu over the parameter. No need to have the duck selected. If you want to freeze the entire bline just do that over the Bline Point List. [[User:Genete|Genete]] 07:48, 29 April 2008 (EDT)&lt;br /&gt;
::Yes, but it would be nice to have opportunity to add waypoint to parameer which not have any ducks yet (i.e. non-animated parameter). --[[User:Zelgadis|Zelgadis]] 08:33, 29 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatically split tangeants ===&lt;br /&gt;
&lt;br /&gt;
Holding shift while moving tangeant ducks should automatically split them. They can be rejoined if necessary through the context menu as they are now.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Dev:Wish_list&amp;diff=7176</id>
		<title>Dev:Wish list</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Dev:Wish_list&amp;diff=7176"/>
				<updated>2008-05-22T16:49:08Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Wishes */ smartrendering and render time calculation&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''''Warning''''': We need more people working on the code if we are going to be able to achieve all the feature requests.&lt;br /&gt;
&lt;br /&gt;
Got a great idea for a new feature? Just add it here, or on the [http://sourceforge.net/tracker/?group_id=144022&amp;amp;atid=757419 feature requests tracker]. Before you do, please check the [http://svn.voria.com/code/ETL/trunk/TODO etl], [http://svn.voria.com/code/synfig-core/trunk/TODO synfig] and [http://svn.voria.com/code/synfig-studio/trunk/TODO synfigstudio] TODO files for similar ideas. Please add a rating of how essential this feature is to your workflow according to the following scale:&lt;br /&gt;
&lt;br /&gt;
#&amp;quot;Well, it might be nifty. To someone.&amp;quot;&lt;br /&gt;
#&amp;quot;I probably would make use this&amp;quot;&lt;br /&gt;
#&amp;quot;It's not essential, but I'd really like to have this at my disposal.&amp;quot;&lt;br /&gt;
#&amp;quot;Synfig would be soooo much better with this change&amp;quot;&lt;br /&gt;
#&amp;quot;I can't/won't use Synfig without it!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== Wishes ==&lt;br /&gt;
&lt;br /&gt;
===Render time approximation===&lt;br /&gt;
Synfigstudio should get a button in the render dialog, which calculates the total render time for the actual settings (frames per second, length of the film, resolution, output format) It should testrender 1 picture, when the amount of total frames is below 1000. Over 1000 frames, it should testrender 10 pictures for more precise calculation.&lt;br /&gt;
&lt;br /&gt;
--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
===Smartrendering===&lt;br /&gt;
I have made 25,000 small png-pictures with my 800Mhz computer in about 45 minutes. Synfigstudio did calculate each single frame of it. Nothing changed in this picture, so it does only need to get written to disk for the amount of pictures, until the next change (animation) has an effect on the output picture. This should save time for bigger projects with thousands of pictures.&lt;br /&gt;
&lt;br /&gt;
--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)   &lt;br /&gt;
&lt;br /&gt;
=== get_color method in text and radial blur ===&lt;br /&gt;
&lt;br /&gt;
[5] Without get_color method distorion produces artifacts &lt;br /&gt;
[http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1831355&amp;amp;group_id=144022&amp;amp;atid=757416 bug  1831355]. So I would like to get this problem fixed before doing something else. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== Full functional of group dialog ===&lt;br /&gt;
&lt;br /&gt;
[5] Group dialog is broken now [http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1796833&amp;amp;group_id=144022&amp;amp;atid=757416 bug 1796833]. So we should get old features work right before making new one. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== import/export .swf files ===&lt;br /&gt;
&lt;br /&gt;
very important productivity feature&lt;br /&gt;
&lt;br /&gt;
=== import/export .svg frames sequence, and/or .svg animations ===&lt;br /&gt;
&lt;br /&gt;
very important productivity feature&lt;br /&gt;
&lt;br /&gt;
=== a realtime .sif synchronized text window ===&lt;br /&gt;
&lt;br /&gt;
just like the xml editor of Inkscape, or the html editor in Dreamweaver (this is hugelly useful for productivity)&lt;br /&gt;
&lt;br /&gt;
I thinks scripting API can be implement in this way. For example you make XML DOM like implementation for python which alows to change DOM tree from python code and see chenges in canvas. By this way you can implement import/export scripts. Automation scripts. And a lot of different things. Even synchronization of animation between blender and synfig. --[[User:AkhIL|AkhIL]] 23:10, 26 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== choosing colour from gimp/inkscape palettes ===&lt;br /&gt;
&lt;br /&gt;
very useful when you need some colour comformity of what you're doing &lt;br /&gt;
&lt;br /&gt;
=== Good high-level documentation of the source code ===&lt;br /&gt;
&lt;br /&gt;
(2) It'd be nice if a newbie could quickly navigate around the source code. The best thing to do would be to add top-level comments in each file, explaining what that file does, a README.TXT in each directory, explaining what's in that directory. This would be pretty fast and easy to do, and make it much easier for new programmers to join. &lt;br /&gt;
&lt;br /&gt;
Time permitting, it would also be good to document on a high level what the data structures are, but that's harder, since those tend to evolve, and it is often difficult to keep in sync. It would also be useful to document what individual functions do (just a one-liner high-level description), but that also takes more time.&lt;br /&gt;
: There is a page link in the wiki that connect to the [http://www.synfig.com/doc Synfig API Documentation]. I think this link should be highlighted to be more accessible for newbies contributors and mature developers (the link was found [[Releases/DeveloperPreview#Support | here]]). --[[User:Genete|Genete]] 10:02, 11 December 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Mathematical functions to animate ===&lt;br /&gt;
(2/4) If you want to make a waving flag, it would be handful a sine function, tuned with random correctors, for example. &lt;br /&gt;
: -This should generate waypoints each 1, 2, 4 frames or any other step at artist's wish.&lt;br /&gt;
: -When applying a function you can add it to current values, add it to 1st frame values or simply override old values. Perhaps other options (such multiplication) would be fine, too. Something like texture editor in [http://www.artofillusion.org Art of Illusion], perhaps.&lt;br /&gt;
Perhaps it would be useful reusing the [http://www.gnu.org/software/octave/ Octave] source code to parse mathematical expressions.&lt;br /&gt;
I have rated this wish with a '2' because undoubtly many users will not be familiar to mathematical concepts, but for those who will be, I'd rate it with a 4. It would be possible to make a ball describing a parabolic moving in no time.&lt;br /&gt;
[[User:ajotatxe|ajotatxe]] 20 November 2007&lt;br /&gt;
: dooglus can probably chime in better than I here (see his example of balls on mathematical paths at http://uk.youtube.com/watch?v=YTpSfUthuVE ), but I believe that this is already possible.  Synfig does support a variety of mathematical transforms for parameters, although the way you do this is by no means intuitive.  (You might also want to check out the preambletaffy.sifz example for an easier approach to a waving flag. I know you were just using that as an example, but for the record...) [[User:Pxegeek|Pxegeek]] 00:58, 21 November 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
: I'd also rate it with a (4) (and updated the rating accordingly), not for this special case, but to make many workarounds much easier.  Simulating [Parabolic Shot|free fall], for example, would be a lot easier with real formulas.  I don't know, though how easy it will be to implement, maybe waiting for a scripting interface to be implemented is better than hacking this feature in an ad-hoc manner.  --[[User:Rubikcube|Rubikcube]] 16:38, 29 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Warning about editing bizarre things in animate editing mode ===&lt;br /&gt;
(3.5) It seems to have little sense animate certain things like Blend Method or Type of Feather. It would be very nice that the program asked comfirmation if you change these attributes in animate editing mode. If you do want to, you would have three options: &amp;quot;Yes, never ask&amp;quot;, &amp;quot;Yes, never ask for this attribute&amp;quot;, &amp;quot;No&amp;quot;. I guess that internally, this attributes has integer type (or something like that) and the attributes that you normally want to animate, float type, so I think that this feature is relatively easy to implement. My English is not very good, so please feel free to fix this post.&lt;br /&gt;
[[User:ajotatxe|ajotatxe]] 20 November 2007&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bones with FK &amp;amp; IK + grouping of objects into folders ===&lt;br /&gt;
&lt;br /&gt;
(1) Bones cane move specific vector assigned to them or the bones can have envelopes that move the vectors within their field of influence, much Like Anime Studio/Moho does. It's quite a time saving process of animating. Objects created can be saved into separate groups or folders using the same system as Anime Studio/Moho -Shadowphoenix 27/8/2007&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Animated sketch ===&lt;br /&gt;
&lt;br /&gt;
(1) it would be great, if the tool Sketch was animatable (for example, in a form of a special sketch-layer). --Zelgadis 2007-06-14&lt;br /&gt;
&lt;br /&gt;
=== Duck for Amount value in Zoom layer ===&lt;br /&gt;
&lt;br /&gt;
(2) It would be nice if Amount value in Zoom layer was controlled by additional duck. --[[User:Zelgadis|Zelgadis]] 02:49, 29 December 2007 (EST)&lt;br /&gt;
: I found that I can better use Warp layer instead of Zoom to change size. But it'd be nice to have Amount duck for Zoom layer anyway...&lt;br /&gt;
:: The Amount parameter works exponentially; each time you add 1 to the Amount, the image is zoomed by a further factor of e (= 2.71828 or so).  Would a duck be any use if it just controlled the value of Amount in a linear way?&lt;br /&gt;
:: Workarounds include: export Amount, select it in the children dialog.  Whatever's selected in the children dialog shows a duck.  You can adjust it using that duck.&lt;br /&gt;
:: Also, if you use a Stretch layer, convert the Amount to Composite, export the X-Axis and connect it to the Y-Axis, then you have a duck-controllable fixed-aspect zoom. -- [[User:Dooglus|dooglus]] 15:32, 15 January 2008 (EST)&lt;br /&gt;
::: Yeah I found this workaround, but it's to much actions - i prefer better use Warp or Stretch layers. Why not the link Amount duck and Amount value with logarithmic function? ;) --[[User:Zelgadis|Zelgadis]] 10:33, 17 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatic colour palette optimisation ===&lt;br /&gt;
&lt;br /&gt;
(0) it would be nice to use libcontrast [http://david.navi.cx/blog/?p=132] [http://david.navi.cx/blog/?p=94] [http://david.navi.cx/blog/?p=99] [http://svn.gnome.org/svn/xchat-gnome/trunk/src/libcontrast/] to automatically adjust selected or all the palette items for best visual contrast. It would also be interesting to have a layer that uses this code to filter the image.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arbitrary Color Channels ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; The ability for the user to create any number of custom channels for various purposes.&lt;br /&gt;
&lt;br /&gt;
=== Autorecover History ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; It would be great if autorecover could also recover the associated history of a file in the event of a crash.&lt;br /&gt;
&lt;br /&gt;
=== Layer Convert ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;(4)&amp;lt;/strike&amp;gt; (2) &amp;amp;mdash; The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''&lt;br /&gt;
&lt;br /&gt;
=== Vector fill bucket ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[Region Layer|region layer]]). &amp;lt;p&amp;gt;Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;If this is implemented, it will probably be necessary to change the existing &amp;quot;fill&amp;quot; tool's name and icon to a &amp;quot;color injector&amp;quot; (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.&lt;br /&gt;
&lt;br /&gt;
*Inkscape has a very innvative version of this tool. Maybe you can just grab the code from there and integrate it in synfig? --[[User:SvH|SvH]] 01:37, 14 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== [[redraw tool]] ===&lt;br /&gt;
&lt;br /&gt;
(4-5) &amp;amp;mdash; Intutive reshaping of path-based layers. See link.&lt;br /&gt;
&lt;br /&gt;
=== [http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance] ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; This should solve all complaints about the layout, without requiring Synfig to be &amp;quot;just like program (x)&amp;quot;. See [[UI Reloaded]] for progress on this.&lt;br /&gt;
&lt;br /&gt;
=== Feedback for [[Smooth Move Tool]] ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; This tool does what a lot of folks are looking for, warping selected ducks in a &amp;quot;soft&amp;quot; fashion. But it's not very obvious what sort of effect it will have, from the tool's interface. It needs some sort of momentary center-of-action and radius indicator at the very least. Perhaps an &amp;quot;influence gradient&amp;quot; overlaid on the canvas once Synfig's core is sped up?&lt;br /&gt;
&lt;br /&gt;
=== Networkability ===&lt;br /&gt;
&lt;br /&gt;
(2) &amp;amp;mdash; Like Inkscape's &amp;quot;inkboard&amp;quot; feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option. This should probably farm off all the networking stuff to the telepathy framework so that synfig doesn't have to deal with all the account/etc issues.&lt;br /&gt;
&lt;br /&gt;
=== Intuitive tangent modification ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.&lt;br /&gt;
&lt;br /&gt;
-Agreed; blender does this with its IPO curves, and it's a really efficient way to work.&lt;br /&gt;
&lt;br /&gt;
=== Plugin API ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
=== Python support ===&lt;br /&gt;
&lt;br /&gt;
(1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.&lt;br /&gt;
&lt;br /&gt;
I suuose to join this request with [[Wish_list#a_realtime_.sif_synchronized_text_window]]. We can implement python access to XML DOM and write XML Editor in python. --[[User:AkhIL|AkhIL]] 06:54, 30 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== mod_synfig ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; For Apache. Render .sif to some format like png/mng on access.&lt;br /&gt;
&lt;br /&gt;
=== synfig nsplugin ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; Let Mozilla and Mozilla-based view synfig files in-browser.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Align function ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; Align objects at a common border (as in Inkscape)&lt;br /&gt;
&lt;br /&gt;
=== Improved SVG import ===&lt;br /&gt;
&lt;br /&gt;
(4) &amp;amp;mdash; Currently, all importing an SVG does is render it in ImageMagick. What I want is the ability to import the SVG document so that all the shapes, etc. of the SVG document show up as their equivilant synfig layers - i.e. if I had put them there myself. I'm trying to write a patch for this but the codebase is mostly undocumented. [[User:KMeist|KMeist]] 16:38, 25 Feb 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
[[svg2synfig]] could be incorporated using an open source XSLT processor. --[[User:Dmd|Dmd]] 13:34, 26 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Gradient Paint Tool ===&lt;br /&gt;
&lt;br /&gt;
How about a tool that can 'paint' a gradient object.  For example the options would be width and gradient type, one would make a stroke with the tool and the gradient would be automatically applied inside of the outline (set by width).  This would save the trouble of having to the all the encapsulation stuff. (Actually any tool that makes creating gradient one step would be good).--[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bone Animation Tools ===&lt;br /&gt;
&lt;br /&gt;
Bone system with inverse kinematics, very important for quick animation. You put bones on a drawed man and you can animate him like a puppet. I'm using that in Moho (lost marble product).--[[User:Ziolive|ziolive]] 23 Aug 2006&lt;br /&gt;
*I would find this very useful too. I think it is called '''rigging'''(4/5) --[[User:SvH|SvH]] 01:33, 14 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== AVI Backgrounds ===&lt;br /&gt;
Is there any way I can add an avi as a background so I could add facial expressions to a stop-motion animated figure. [zotz here, I was thinking DV background or extra timeline. I would like to mix animations with live footage. rating (3/4)]&lt;br /&gt;
&lt;br /&gt;
=== Character tool on Tool Options Dialog ===&lt;br /&gt;
&lt;br /&gt;
I want to use the as a character generator for a TV show. By using chroma key hide the background.  Even better interface to a video overlay card with Alpha blending.&lt;br /&gt;
&lt;br /&gt;
=== Collect for Publication ===&lt;br /&gt;
&lt;br /&gt;
(3/4) - (zotz) Menu item, functionality that would collect alll files referenced in a sif and place them all in a tgz for sending elsewhere or publishing anumations in source form.&lt;br /&gt;
&lt;br /&gt;
=== Object Library ===&lt;br /&gt;
&lt;br /&gt;
(3/4) - (zotz) Haven't thought this all through yet, but synfig could come with a library of categotrised &amp;quot;objects&amp;quot; with a copyleft license (GPL?  CC BY-SA?) An animation clip art type deal.&lt;br /&gt;
**I'd suggest this should be public domain and distributed by openclipart.org -- --[[User:PaulWise|pabs]]&lt;br /&gt;
&lt;br /&gt;
=== Flash Export ===&lt;br /&gt;
&lt;br /&gt;
(3/4) Well, might just be me but if there was a posiblity to  export in .swf or .fla, I think the project might become a lot more popular.[[User:Conceit|Conceit]]&lt;br /&gt;
&lt;br /&gt;
(4/5) I wholeheartedly agree. I would definitely use synfig more if this feature were added and it would most definitely increase popularity. [[User:cdj05a|cdj05a]]&lt;br /&gt;
&lt;br /&gt;
=== Single window ===&lt;br /&gt;
&lt;br /&gt;
Depending on individual desktop setups, single window is sometimes preferable to many  windows. Can we have a single-window option?&lt;br /&gt;
&lt;br /&gt;
Also, even with many windows, Windows-users especially might find it better if all the windows only appeared as a single one on the taskbar.&lt;br /&gt;
&lt;br /&gt;
=== Line width tool ===&lt;br /&gt;
(4) It will be good to have a tool for easy changing line width. There was a such tool in earlier versions, but it's not usable. I'm often use variable line width, when drawing in synfig, so it is important for me. -- [[User:Zelgadis|Zelgadis]] 2007-09-09&lt;br /&gt;
&lt;br /&gt;
: It is [[FAQ#Where did the polygon, draw, sketch, and width tools go?|still available]].  Also, you can turn on the width ducks, using Alt-5. -- [[User:Dooglus|dooglus]] 12:18, 9 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
:: It is available, but I never was able to figure out how it works. Alt-5 works, but it is hard to set width to zero, for example. -- [[User:Zelgadis|Zelgadis]] 2007-09-10&lt;br /&gt;
&lt;br /&gt;
::: Are you wanting something that works on one vertex at a time?  Or all the vertices in an area?  Apparently the width tool was designed to work on a bunch of vertices at once.  I didn't figure out how it works though, either. -- [[User:Dooglus|dooglus]] 16:57, 10 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
:::: Width tool is surely a mystery. :) I'm waiting for something that works on one vertex at time. I liked the way as width was changed in Moho (Anime Studio now) - there was a special width tool and holding left mouse button on the vertex and moving cursor left decreasing width value, moving right - increasing. Maybe it make sense to rework Width tool in such way. -- [[User:Zelgadis|Zelgadis]] 2007-09-13&lt;br /&gt;
&lt;br /&gt;
=== Export Wizard ===&lt;br /&gt;
&lt;br /&gt;
(2/4) Conversion and export to other file formats (mpg, avi, flash formats, others, and the synfig format) with a step by step wizard for choosing format and place of saving. Similar to Gimp's saving of .png files but for movie/video type files. --&lt;br /&gt;
[[User:Hiddenghost|hiddenghost]]&lt;br /&gt;
&lt;br /&gt;
=== Using Synfig as a portable app ===&lt;br /&gt;
&lt;br /&gt;
(3) This isn't really a feature request (though it could be) but I was wondering if synfig could be used as a portable application (as in www.portableapps.com). Does the windows install require registry access? i really want to use Synfig at work, but I'm reluctant to install it just in case it leave footprints in the regisitry or something, and it would be sweet to use it on my travels as well. Only thing is, I can't test it out at home because I am using Linux.&lt;br /&gt;
See also: http://portableapps.com/node/5761&lt;br /&gt;
[[User:Zenoscope|zenoscope]]&lt;br /&gt;
&lt;br /&gt;
This isn't currently possible without modifying the source code. That has been on my TODO list for ages [[User:PaulWise|pabs]] 01:17, 26 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Allow organize child valuenodes in an hierarchy ===&lt;br /&gt;
(3-2) And allow maintain the organization once the file is saved. At the moment they are reordered in alphabetical order which is useless and annoying.&lt;br /&gt;
&lt;br /&gt;
=== Triangle sliders to be always visible ===&lt;br /&gt;
(3) I would like that the triangle sliders from [[Colors Dialog]] and [[Gradient Editor Dialog]] were visible whatever color or channel you're editing. Some times when the color or channel is to bright or light the slider is difficult to distinguish. --[[User:Genete|Genete]] 14:30, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== XICC support ===&lt;br /&gt;
&lt;br /&gt;
It would be cool if synfigstudio had support for [http://burtonini.com/blog/computers/xicc XICC].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Area to Edit ===&lt;br /&gt;
&lt;br /&gt;
An option like blender - select area to update would be nice, so the only part of the image that updates when you add or change something is in the selected area&lt;br /&gt;
&lt;br /&gt;
ie. when working on a complex composition, studio doesn't know, when I tweak a tiny part of the composition, that only that part needs redrawing, so it redraws the whole thing.  It would be good if there was some way of telling it which part to focus on. -- [[User:Dooglus|dooglus]] 04:02, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Histograms ===&lt;br /&gt;
&lt;br /&gt;
 01:23  * AkhIL wish to have histograms and luma/color scope like [http://mac.softpedia.com/progScreenshots/Avid-Xpress-DV-Screenshot-14207.html] in synfig&lt;br /&gt;
&lt;br /&gt;
I've looked at those pictures but don't know what they're showing.  Can you describe what those scopes are doing, and what the histograms display?  ie. what are the X and Y axes of the histograms? -- [[User:Dooglus|dooglus]] 04:07, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
First look this description in blender wiki [http://wiki.blender.org/index.php/Manual/VSE_Modes]&lt;br /&gt;
&lt;br /&gt;
Ok There is four things.&lt;br /&gt;
* Upper left is Lumascope (Luma Waveform in blender). X-Axis represents image's X-Axys. Y-Axis  is average luminescence of column of pixels.&lt;br /&gt;
* Upper right is Chromascope (Chroma Vectorscope in blender). Just look description on blender wiki.&lt;br /&gt;
* Lower left is like Lumascope but for each channel &lt;br /&gt;
* Lower right is histograms. X is luminescence and Y is count of pixels with such luminiscence.&lt;br /&gt;
&lt;br /&gt;
=== Sound Layer ===&lt;br /&gt;
&lt;br /&gt;
(4) It would be a very good improvement if the sound system were implemented into synfig in [[Sound Layer | this]] way. --[[User:Genete|Genete]] 07:46, 8 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Rearrange the view of waypoints for Canvas param ===&lt;br /&gt;
As reported in [http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1888858&amp;amp;group_id=144022&amp;amp;atid=757416 Bug #1888858] waypoints are not displayed for canvas switch events.&lt;br /&gt;
I suggest to rearrange waypoints display according to [[Media:Canvas_prop.png|this scheme]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Width weigths ===&lt;br /&gt;
Is it possible to add &amp;quot;weigths&amp;quot; for widths? ^_^ I.e. width changes not all the way along the segment. Maybe something like a duck on bline which indicates the region where the width of current vertex isn't changed.&lt;br /&gt;
[[Media:width-proposal.png|Illustration here.]]&lt;br /&gt;
&lt;br /&gt;
More ideas around this concept in [http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-04-16.log this conversation]. Although the log of that day is very interesting the lines related to this idea are from 22:38 to 23:43. [[User:Genete|Genete]] 17:51, 16 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Improved Colour Dialog ===&lt;br /&gt;
How easy is it to stick in a colour square/wheel? Messing with sliders is somewhat obstructive.&lt;br /&gt;
&lt;br /&gt;
=== Insert Waypoints ===&lt;br /&gt;
A button to create a waypoint for every selected duck, in its current position. Moving each duck up a bit and down again quickly gets tedious.&lt;br /&gt;
:If the duck in question has already a waypoint then you don't need to move it to create a new waypoint. Just select the corresponding parameter in your child list panel and select 'Add Waypoint' from the right click context menu over the parameter. No need to have the duck selected. If you want to freeze the entire bline just do that over the Bline Point List. [[User:Genete|Genete]] 07:48, 29 April 2008 (EDT)&lt;br /&gt;
::Yes, but it would be nice to have opportunity to add waypoint to parameer which not have any ducks yet (i.e. non-animated parameter). --[[User:Zelgadis|Zelgadis]] 08:33, 29 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatically split tangeants ===&lt;br /&gt;
&lt;br /&gt;
Holding shift while moving tangeant ducks should automatically split them. They can be rejoined if necessary through the context menu as they are now.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=User:SvH&amp;diff=7174</id>
		<title>User:SvH</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=User:SvH&amp;diff=7174"/>
				<updated>2008-05-21T12:16:25Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:Steve2737623.png|200px|thumb|left|This is, how i don't look like]]&lt;br /&gt;
Hi, my name is Stefan! I am a german translator and do currently translate synfig to my language. I try to help this project as much as i can to improve this program. I am no coder, so i try to focus on everything else.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not the big artist, but almost all things and pieces i draw in inkscape, i upload to [[http://openclipart.org/media/people/StefanvonHalenbach openclipart.org]] under the public domain license. I hope, that some day it would be possible to import SVG-graphics natively in synfig, because i try to draw as many things (in vectors) i could, for a 2-D animation film. Such things like different walls, windows, walkways, cars, backgrounds.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=User:SvH&amp;diff=7173</id>
		<title>User:SvH</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=User:SvH&amp;diff=7173"/>
				<updated>2008-05-21T05:18:05Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:Steve2737623.png|thumb|left|This is, how i don't look like]]&lt;br /&gt;
Hi, my name is Stefan! I am a german translator and do currently translate synfig to my language. I try to help this project as much as i can to improve this program. I am no coder, so i try to focus on everything else.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=File:Steve2737623.png&amp;diff=7172</id>
		<title>File:Steve2737623.png</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=File:Steve2737623.png&amp;diff=7172"/>
				<updated>2008-05-21T05:15:52Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: My own drawing with Inkscape.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;My own drawing with Inkscape.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=User:SvH&amp;diff=7171</id>
		<title>User:SvH</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=User:SvH&amp;diff=7171"/>
				<updated>2008-05-21T05:13:06Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: New page: Hi, my name is Stefan! I am a german translator and do currently translate synfig to my language. I try to help this project as much as i can to improve this program. I am no coder, so i t...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hi, my name is Stefan! I am a german translator and do currently translate synfig to my language. I try to help this project as much as i can to improve this program. I am no coder, so i try to focus on everything else.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Doc:How_Do_I&amp;diff=7168</id>
		<title>Doc:How Do I</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Doc:How_Do_I&amp;diff=7168"/>
				<updated>2008-05-20T10:49:25Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Increase performance by optimizing during compilation time? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--Categories--&amp;gt;&lt;br /&gt;
[[Category:Tutorials]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Feel free to add your own questions here or [[Contact|contact]] us with them. Or put them on the [[Wiki Wish List]].&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Insert some text? ==&lt;br /&gt;
&lt;br /&gt;
With recent development versions, there is a text tool. If you are using 0.61.08 or earlier, use right click on your canvas and choose Layer &amp;gt; New &amp;gt; Other &amp;gt; Text.&lt;br /&gt;
&lt;br /&gt;
== Apply a gradient to an object instead of the entire canvas? ==&lt;br /&gt;
&lt;br /&gt;
# Create the region you want to fill with a gradient, and the gradient layer, if you haven't already.&lt;br /&gt;
# Make sure that the gradient layer is above the region layer in the [[Layers Panel]].&lt;br /&gt;
# Select both layers, right click, and select [[Encapsulate]].&lt;br /&gt;
# Expand the new [[Paste Canvas|Inline Canvas]] layer if it's not already, and select your gradient layer.&lt;br /&gt;
# In the [[Params Panel]] select the [[Blend Method]] parameter, and choose [[Blend Method#Onto|Onto]] from the drop-down menu.&lt;br /&gt;
&lt;br /&gt;
The gradient will clip to the visible area of the region below it inside the [[Paste Canvas|Inline Canvas]]. (and any other layers in that section).&lt;br /&gt;
&lt;br /&gt;
== Show or hide a layer, or fade the effect of a blur? ==&lt;br /&gt;
In the [[Params Panel]], look for an option labeled [[Amount Parameter|Amount]] - this controls how much of the blended result of the layer is composited with the blend of the layers beneath it.&lt;br /&gt;
&lt;br /&gt;
In other words, for a typical layer, this will 'fade it out'. For a [[Blur Layer]] set to &amp;quot;[[Blend Method#Straight|Straight]]&amp;quot;, this will fade ''between'' the blurred version and the unblurred version of the canvas. If you want it to become less blurry, adjust the [[Blur Layer#Size|Blur Layer's 'size' parameter]].&lt;br /&gt;
&lt;br /&gt;
== Fill an outline? ==&lt;br /&gt;
(Requested by [[User:Karlb|Karlb]])&lt;br /&gt;
&lt;br /&gt;
There are several options:&lt;br /&gt;
* The easiest way is to link a new region layer to the outline's shape.&lt;br /&gt;
*# Select the outline you want to fill.&lt;br /&gt;
*# In the Params Panel, right-click the Vertices parameter, select &amp;quot;Export&amp;quot;, enter a name for the shape, and hit return.  This will export the shape of the outline, making it visible in the Children dialog.&lt;br /&gt;
*# In the Children dialog, open the ValueBase Nodes tree and select the name you just saved the shape as.&lt;br /&gt;
*# From the [[Layer Menu]] (either context-click on the [[Layers Panel]] or use the [[Canvas Menu Caret]]) create a new [[Region Layer]] by selecting &amp;quot;New Layer -&amp;gt; Geometry -&amp;gt; Region&amp;quot;. Ensure that the created layer is selected.&lt;br /&gt;
*# In the parameter dialog, right-click the Vertices parameter and click &amp;quot;Connect&amp;quot;.&lt;br /&gt;
*# Now, if you don't need exported shape, you can unexport it: right click name of the shape in the Children dialog and click &amp;quot;Unexport&amp;quot;.&lt;br /&gt;
* Similar to the above, but using a different method:&lt;br /&gt;
*# Create a new region layer as above, and leave it selected.&lt;br /&gt;
*# Don't make any changes to the outline layer, which you want to fill! (see the Tier 5 on the [[Linking]] page for details).&lt;br /&gt;
*# Select both layers in the [[Layers Panel]] This will display only the parameters shared by both layers in the [[Params Panel]].&lt;br /&gt;
*# Context-click on the [[Vertices Parameter]], and select [[Linking|Link]].&lt;br /&gt;
*# The [[Region Layer]] will snap to the shape of the [[Outline Layer]].&lt;br /&gt;
* When you create an [[Outline Layer|outline]] with the [[Bline Tool]] that you intend to be a filled area as well, make sure you select the Fill checkbox in the [[Bline Tool#Options|tool options dialog]]. Obviously, this doesn't help much if you realise later that you needed a fill here.&lt;br /&gt;
* If you are using the [[draw tool]], there is a button at the bottom of the [[draw tool#Options|tool options dialog]] labeled &amp;quot;Fill Last Stroke&amp;quot;, which creates a new [[Region Layer]] and links its shape to the previously drawn outline. Unfortunately, it doesn't work as of Synfig Studio v0.61.04.  It has been fixed in the current SVN version of the code.&lt;br /&gt;
* Create a [[Region Layer|region]] with the same number of ducks, and manually link each duck. If you want a region that depends on multiple outline layers, this is really your only choice for now.&lt;br /&gt;
* Use the draw tool, select only the outline to fill, draw a stroke roughly following the outline and make sure you're holding the Control key when you left go of the mouse button at the end of the stroke.  This doesn't work 100% right at the moment.&lt;br /&gt;
&lt;br /&gt;
== Dock windows together? ==&lt;br /&gt;
&lt;br /&gt;
*To dock (join) separate windows into one you must drag the tab ''icons'' for each of the tools into another window. &lt;br /&gt;
*You can create subdivisions inside the windows by dragging the icons into the side tabs (located around the edges, the look like rectangles). &lt;br /&gt;
*Tool tabs inside the window can be arranged by dragging them on top of one another, therefore changing the order.&lt;br /&gt;
*''How Do I min/maximize all Synfig windows on a Windows pc''? There must be an easy way/tool to do this?&lt;br /&gt;
&lt;br /&gt;
== Use an external bitmap? ==&lt;br /&gt;
&lt;br /&gt;
* In the image menu (&amp;gt;) choose file--&amp;gt;import. PNG with alpha channel works fine.&lt;br /&gt;
* To animate it without accidental stretching, right-click on the layer and choose encapsulate. You can then animate the position of the new &amp;quot;Inline Canvas&amp;quot; layer instead of the bbox.&lt;br /&gt;
&lt;br /&gt;
== Use an external Vector? ==&lt;br /&gt;
&lt;br /&gt;
Synfig doesn't yet support vector import because no-one has written an import process yet. You can use the Svg2synfig [[Converters|converter]], or import it as a bitmap and trace over it in synfig. If you want to implement vector import we would gladly accept your patch.&lt;br /&gt;
&lt;br /&gt;
== Close a bline? ==&lt;br /&gt;
&lt;br /&gt;
* Right click on the starting point and then click on loop bline.&lt;br /&gt;
&lt;br /&gt;
Note: It doesn't work unless the initial point has a tangent - ie the first segment is curved. But you can hide tangent ducks (Alt+3, or &amp;quot;Caret Menu &amp;gt; View &amp;gt; Show/Hide Ducks &amp;gt; Show tangent ducks&amp;quot;) and process as described. Don't forget to press (Alt+3) after that to show tangent ducks again.&lt;br /&gt;
&lt;br /&gt;
== How do I transform encapsulated objects? ==&lt;br /&gt;
&lt;br /&gt;
* Right click on the Encapsulated object in the Layer dialog and choose &amp;quot;select all child layers&amp;quot;. Then you select the ducks you want to transform (usually just all of them, like for rotating the object), and the rotate or scale tool and do the work.&lt;br /&gt;
&lt;br /&gt;
== Make objects go behind each other, without moving layers? ==&lt;br /&gt;
&lt;br /&gt;
You'll notice each layer you make has a number in the z depth column in the Layers Panel. Say you have 3 layers, they will be numbered 2 (lowest, e.g. a square) 1 (eg a circle) 0 (highest, the default, e.g. a line). In order to make layer 1, the circle, pass behind layer 2, the square, change its z depth to be 3 or more. The z depth of the circle needs to be greater than 2 in order to be behind the square. To make the square on top of everything, you'd change its z depth to -1 or less. &lt;br /&gt;
&lt;br /&gt;
Positive numbers on the z axis go into the screen, and negative numbers go out of the screen, towards the viewer.  &lt;br /&gt;
&lt;br /&gt;
It is possible to animate this effect, but each layer is discrete. They seem to go from 0 to 0.9999.&lt;br /&gt;
&lt;br /&gt;
In addition, objects in encapsulated layers can only go behind other objects in the same encapsulated layer. However an encapsulated layer can go behind another encapsulated layer.&lt;br /&gt;
&lt;br /&gt;
== Copy a complex convert combination between parameters of different layers? ==&lt;br /&gt;
&lt;br /&gt;
For example: you want to copy a complicated [[Convert|conversion]] type that you have in one parameter from a layer, to other parameter (maybe not a root parameter, but a sub-parameter) of other layer. If you [[Export|export]] the complicated conversion type from the original layer and then go to the other layer and select [[Connect]] (right click and the exported and the parameter both selected) then you have the parameter form the second layer to be exactly the same than the original one. But there is a drawback: if you modify one of the sub-parameters in the complicated conversion type (e.g. you change the value of one of them) then automatically the same sub-parameter of the other layer is changed.&lt;br /&gt;
&lt;br /&gt;
How can you copy the conversion but allow modify the sub-parameters independently on each layer? &lt;br /&gt;
&lt;br /&gt;
Once you have achieved the complex conversion type in the original layer, &amp;lt;u&amp;gt;don't export the root parameter!&amp;lt;/u&amp;gt; If you have done yet [[Export|unexport]] it. (Why?. You will understand it later.) Now duplicate the original layer. Then you should obtain the same layer with the same conversion type placed at the same parameter (but not exported). NOW export the parameter from the duplicated layer. Then go to the (sub) parameter of the layer where you want to copy the complex conversion type and Connect it to the just exported parameter form the duplicated layer. Now delete the duplicated layer (!). Then the exported [[ValueNode]] still undeleted and the layer where you wanted to copy the complex convert type have a (sub) parameter connected to it. You can [[Export|unexport]] the ValueNode or not. It is up to you. But notice that the conversion type is already copied into other (sub) parameter of other layer and they are independent as well as you can change one of them (by modifying the sub-parameters) and the other remains untouched.&lt;br /&gt;
&lt;br /&gt;
== Make an existing animation run at half speed? ==&lt;br /&gt;
&lt;br /&gt;
If you have an animation that runs from 0s to 10s and you want it to run at half speed from 0s to 20s, how can you do that?&lt;br /&gt;
&lt;br /&gt;
* Either: encapsulate it, and use the 'time offset' parameter in the encapsulation layer to slow it down:&lt;br /&gt;
** Right-click 'time offset' in the encapsulation layer, convert&amp;gt;linear, rate -0.5 offset 0.  That means offset the time by -0.5 seconds per second - or in other words, run at half speed&lt;br /&gt;
** Or, putting waypoints on the 'time offset' param would work too: 0 at 0s and -10 at 20s.  (The choice between using a linear convert and valuenodes is entirely up to you.  They both achieve the same result in this simple case).&lt;br /&gt;
&lt;br /&gt;
* Or: use a [[Time Loop Layer]].  The first method seems better and more intuitive in this case, but there are ways of getting the same effect from the Time Loop layer.  Perhaps the Time Loop layer is better if the animation doesn't run from 0s, but from some other time.  Anyway: put a Time Loop layer over the layers you wish to slow down, and:&lt;br /&gt;
** Either: set duration to 0, local time to 0, convert-&amp;gt;linear the link time and set rate to 0.5 - this slows the animation down *to* 50% of its original speed;  use bigger rates to slow it down less&lt;br /&gt;
** Or: set duration to 1h (*), link time to 0, convert-&amp;gt;linear the local time and set rate to 0.5 - this slows the animation down *by* 50%; use bigger rates to slow it down more&lt;br /&gt;
(*) if your animation is longer than 1h then set this parameter to EOT (End Of Time) what is the same as Infinite (INF) for a real number but for a time parameter.&lt;br /&gt;
&lt;br /&gt;
== Draw a rectangle with a given width and height? ==&lt;br /&gt;
&lt;br /&gt;
I was asked on IRC how to specify the width and height of a rectangle, rather than having to specify the position of two opposite corners.  Here's how:&lt;br /&gt;
&lt;br /&gt;
* draw a rectangle&lt;br /&gt;
* go to the [[Params Panel]]&lt;br /&gt;
* right-click the 'point 1' parameter and [[Export]]&lt;br /&gt;
* give it a name, &amp;quot;p1&amp;quot; say&lt;br /&gt;
* right-click the 'point 2' parameter and [[Convert]] to [[Convert#Add|Add]]&lt;br /&gt;
* (that's saying that rather than specifying the absolute position of the other point, you want synfig to calculate it for you)&lt;br /&gt;
* (it will make 2 new sub-parameters for 'point 2', and the value used for point 2 will be their sum so we want to tell it to use 'point 1' and your (width,height))&lt;br /&gt;
* open up the sub-parameters of 'point 2' by clicking the triangle to its left&lt;br /&gt;
* go to the [[Children Panel]], open up the values and select the one you exported earlier (p1)&lt;br /&gt;
* right-click the &amp;quot;LHS&amp;quot; parameter in the parameters dialog and [[Connect]] it&lt;br /&gt;
* then enter the width and height you want in the 'RHS' parameter&lt;br /&gt;
&lt;br /&gt;
== Make linked BLine vertices not affected by Rotate layer? ==&lt;br /&gt;
Look at the http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-02-07.log &lt;br /&gt;
See also: [[Convert]].&lt;br /&gt;
&lt;br /&gt;
== Create dashed outlines? ==&lt;br /&gt;
&lt;br /&gt;
If you want to make simple dashed outlines the faster way is proceed like this:&lt;br /&gt;
&lt;br /&gt;
* Create a Curve Gradient and an Outline over the same [[Bline]] using the [[Bline Tool]] options. Check both Outline and Gradient at the [[Tool Options Panel]].&lt;br /&gt;
* Raise up the gradient layer (it is created below the [[Outline Layer]]).&lt;br /&gt;
* Modify the gradient [[Blend Method]] parameter to be Straight Onto. That would render the gradient onto the outline width. Also it wouldn't render the outline, so transparent portions of the gradient are transparent.&lt;br /&gt;
* Check the 'Perpendicular' parameter of the Curve Gradient Layer.&lt;br /&gt;
* [[Convert]] the Gradient Parameter of the Curve Gradient Layer to be one of those types: Stripes or Repeat Gradient.&lt;br /&gt;
* Modify the properties of the sub parameters to achieve the desired effect.&lt;br /&gt;
&lt;br /&gt;
== Render to AVI with higher quality? ==&lt;br /&gt;
&lt;br /&gt;
=== Using raw video ===&lt;br /&gt;
The module used by Synfig to render AVI files is ffmpeg. For the moment there is not interface to control ffmpeg options so you render with a fixed bitrate and quality. If you want the maximum quality in your AVI file, follow these steps:&lt;br /&gt;
&lt;br /&gt;
* Render your animation to yuv420p format. To do that select that target at the drop down list of the render dialog and add the &amp;quot;.yuv&amp;quot; extension to your animation name (without quotes).&lt;br /&gt;
* Once rendered (it would produce a huge size yuv file) you can quickly convert it to AVI using this command:&lt;br /&gt;
&lt;br /&gt;
 ffmpeg -i animation.yuv -sameq animation.avi&lt;br /&gt;
&lt;br /&gt;
Change the animation file name to your one.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Rendering trough png sequence. ===&lt;br /&gt;
Render your sif to png sequence &lt;br /&gt;
 mkdir render&lt;br /&gt;
 synfig my_animation.sifz -o render/frame.png&lt;br /&gt;
Then convert it to movie with ffmpeg&lt;br /&gt;
 ffmpeg -r &amp;lt;frame rate&amp;gt; -i render/frame.%04d.png &amp;lt;more settings from ffmpeg's manual&amp;gt; my_animation.mov&lt;br /&gt;
If you need nice open source format without any tweaks you may try ffmpeg2theora:&lt;br /&gt;
 ffmpeg2theora render/frame.%04d.png --inputfps &amp;lt;frame rate&amp;gt; -o my_animation.ogg&lt;br /&gt;
png takes less disk space then yuv.&lt;br /&gt;
--[[User:AkhIL|AkhIL]] 21:38, 9 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
==Increase performance by optimizing during compilation time? ==&lt;br /&gt;
&lt;br /&gt;
I would like to know what parameters do I need to apply to configure to improve performance. [[User:Genete|Genete]] 11:04, 9 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
To optimize program you should set two environment variables&lt;br /&gt;
 export CFLAGS=&amp;quot;&amp;quot;&lt;br /&gt;
 export CXXFLAGS=$CFLAGS&lt;br /&gt;
&lt;br /&gt;
First flag will be &amp;quot;-O3&amp;quot; (ow three). &amp;quot;-02&amp;quot; is normal optimization. &amp;quot;-03&amp;quot; is hard optimisation.&lt;br /&gt;
&lt;br /&gt;
Now you should get info about your CPU&lt;br /&gt;
 cat /proc/cpuinfo&lt;br /&gt;
&lt;br /&gt;
find your cpu model name&lt;br /&gt;
&lt;br /&gt;
now go to man gcc and searc &amp;quot;-mtune&amp;quot;&lt;br /&gt;
&lt;br /&gt;
find your cpu and add &amp;quot;-mtune=your-cpu -march=your-cpu&amp;quot; to CFLAGS. &lt;br /&gt;
&lt;br /&gt;
Then look at flags from /proc/cpuinfo and search it in gcc manual&lt;br /&gt;
For example I have 3dnow. So I can find &amp;quot;-m3dnow&amp;quot;. For sse I can find &amp;quot;-msse&amp;quot; and &amp;quot;-mfpmath=sse&amp;quot; (can make program unstable). &lt;br /&gt;
&lt;br /&gt;
Finaly you may add &amp;quot;-ffast-math&amp;quot; to disable math checks. But it can make program unstable.&lt;br /&gt;
&lt;br /&gt;
For my AthlonXP I'm using this flags:&lt;br /&gt;
 export CFLAGS=&amp;quot;-O3 -pipe -mtune=athlon-xp -march=athlon-xp -mmmx -msse -m3dnow -mfpmath=sse -ffast-math -funsigned-char -fno-strict-aliasing&amp;quot;&lt;br /&gt;
 export CXXFLAGS=$CFLAGS&lt;br /&gt;
--[[User:AkhIL|AkhIL]] 12:05, 9 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
For my Pentium3 i use the line:&lt;br /&gt;
export CFLAGS=&amp;quot;-O3 -pipe -mtune=pentium3 -march=pentium3 -msse -mfpmath=sse -funsigned-char -fno-strict-aliasing&amp;quot;&lt;br /&gt;
 export CXXFLAGS=$CFLAGS&lt;br /&gt;
&lt;br /&gt;
The additional switches -mmmx and -ffast-math does seem to '''not''' yield any gain in computing performance! So you could leave them out.&lt;br /&gt;
--[[User:SvH|SvH]] 03:46, 20 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
== Granted Wishes ==&lt;br /&gt;
&lt;br /&gt;
=== MNG target filetype ===&lt;br /&gt;
&lt;br /&gt;
The ability to save as/in the Free/Open MNG (.mng) format [http://libpng.org/pub/mng/]&lt;br /&gt;
&lt;br /&gt;
A partial implementation was committed in SVN r470.&lt;br /&gt;
&lt;br /&gt;
It was implemented in svn 986. See [[Render options]]. --[[User:Genete|Genete]] 13:12, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== Optionally display RGB in Hex in Color dialog ===&lt;br /&gt;
&lt;br /&gt;
(3) When colors are quoted as 3 bytes of hexadecimal, you have to convert them to decimal, divide by 255, multiply by 100 to get a number to type into the dialog box.  It's painful to match color schemes for example, with the [http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines Tango Icon Theme style guidelines].  [[User:pxegeek|PXEGeek]] 3/16/07&lt;br /&gt;
&lt;br /&gt;
: Added in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=40dda9d27b5249ee32f62d84c819ff569f078929 svn r354].  You can type 3 or 6 digit hex codes and hit return to use.  3 digit code 36a gives colour 3366aa (each digit is duplicated) -- [[User:Dooglus|dooglus]] 3/18/07&lt;br /&gt;
&lt;br /&gt;
:: Many thanks - already used many times! PXEGeek.&lt;br /&gt;
&lt;br /&gt;
::: Did you notice that you can use single digit codes too?  '5' gives 555555 for instance, giving you 16 equally spaces shades of black through white. -- [[User:Dooglus|dooglus]] 17:51, 25 September 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== Restore Default Layout ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.&lt;br /&gt;
-&amp;gt; I'd like to second this one - especially with the bug where dialog boxes sometime shrink to nothing or offscreen, and no amount of maximizing or minimizing restores them.  The only solution is to kill the windows, and none of the combo options in the dialog menu match the default configuration.  4/4/07 PXEGeek&lt;br /&gt;
&lt;br /&gt;
: Implemented in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=036306f3c2c265a604971728d50fcce258766552 svn r757] -- [[User:Dooglus|dooglus]] 17:48, 25 September 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== General outline / Polygon-based Outline / &amp;quot;Set Tangents to Zero&amp;quot; button ===&lt;br /&gt;
(3.5) I'm no artist, thus my primary form of art is stick figures, not to mention, many interesting animations are done in stick-figure style. Stick figures must be perfectly straight to get the effect across, so when I'm making an outline using B-Curves, it is too time consuming to set the tangents to 0 each time. Similarly, outlines of other shapes like squares, circles and so forth would be very useful. Whichever of the above is easiest, please implement right away. --[[User:Dragontamer|Dragontamer]] 02:35, 19 November 2007 (EST)&lt;br /&gt;
: For perfectly straight lines, click without moving the mouse.  You will get a single point with no tangents.  Outline shapes would require some development, particularly with some thought given to backward compatibility.  A workaround you might consider is to create a duplicate shape with a different color and make the top one slightly smaller, so the outline of the one below shows.  [[User:Pxegeek|Pxegeek]] 21:58, 19 November 2007 (EST)&lt;br /&gt;
:: Well, in general, whenever I click on a point to edit it (say, to make it move somewhere in animation mode), there is a decent chance that I click on a tangent instead. Then, if I want to right click the point itself, I usually right click the tangent marker instead. It isn't that big a deal, but simplicity at the cost of power generally is a good thing, especially when it will save a few mouse clicks. &lt;br /&gt;
:: As for the outlines, yeah, I've tried that and it is a decent solution for now, although it is no replacement for a real outline. I am going to also experiment with a clamp to see if I can make the center of the shape have 100% alpha... but I don't have synfig on the computer I'm on right now. Thanks for the tips Pxegeek. --[[User:Dragontamer|Dragontamer]] 01:58, 27 November 2007 (EST)&lt;br /&gt;
::: You can press Alt+3 to hide tangent ducks. --[[User:Zelgadis|Zelgadis]] 09:27, 27 November 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Copy &amp;amp; Paste/Image Importing ===&lt;br /&gt;
&lt;br /&gt;
(4) I sometimes make graphics in other programs, or use clipart and other images. Would it be possible for Synfig to be able to import images and/or copy and paste them?--Khlieeq 2007-07-19&lt;br /&gt;
Well, it doesn't support Copy &amp;amp; paste from the clipboard, but you can import images using &amp;quot;New Layer -&amp;gt; Other -&amp;gt; Import&amp;quot;.  This will create an Import layer, for which you can then edit the properties to point to the file containing your image.  PXEGeek.  2007-07-19&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Recursive Waypoint Manipulation ===&lt;br /&gt;
&lt;br /&gt;
(4) it is really tiresome to revert changes to waypoints created by manipulating tangent/position ducks or change their interpolation functions. making it possible to right-click-modify the waypoint shown for objects that have some waypoint in a referenced sub-object would be great! -- timonator 2007-06-01&lt;br /&gt;
:You can do it in two ways: changing the interpolation method of the waypoint of paste canvas or editing the keyframe properties. The first allow to modify the waypoints interpolation method for all the waypoints of all the parameters of all the layers that are inside the paste canvas layer. You can right click on the left or right part of the waypoint to edit by a context menu the left or the right interpolation method of the waipoints. The second method would add and modify all the parameters that have any waypoint in the animation. See [[Keyframe]] for more detail. --[[User:Genete|Genete]] 13:10, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Tweening for images developed in other imaging programs ===&lt;br /&gt;
&lt;br /&gt;
It's obvious I am a beginner at image movement, but morphing is not enough: movement across the page is needed.  Thanks for listening. [[User:Comwell@bellsouth.net|Comwell]]&amp;lt;br&amp;gt;&lt;br /&gt;
Imported images can be moved across the page.  They can also be scaled, rotated and deformed.  Was there a specific example you had in mind?  [[User:Pxegeek|pxegeek]]&amp;lt;br&amp;gt;&lt;br /&gt;
:I also would like a way to tween images that have been drawn in other programs. I've had trouble drawing with Bline tool and the drawing tool in Synfig, and I'd rather just draw with a paint brush (like the one in Photoshop). Another problem I have is that Synfig tends to shut down on me every 20 minutes or so, and it's really frustrating even with the auto recover feature, because my sketches disappear. It'd be nice if I'm able to draw all of the keyframes in Photoshop or another image program and import it to Synfig so that Synfig can tween and animate them. Thank you. [[User:xychefoo@gmail.com|Huina]]&lt;br /&gt;
::You CAN use images, drawn in other programs. Just select &amp;quot;File-&amp;gt;Import&amp;quot; from [[Canvas Menu Caret|canvas menu]] --[[User:Zelgadis|Zelgadis]] 01:39, 24 November 2007 (EST)&lt;br /&gt;
:::But how do you animate using images from other sources? I tried to make 2 keyframes with 2 different images, and it doesn't animate. It just stays as 1 picture for the entire render. The closest thing I saw to importing images from another source into Synfig and having it animate is the Walking Cycle Tutorial, but I would still have to trace the images to make it animate. As I said earlier, I'm not entirely fond of using the draw/Bline tool.  [[User:xychefoo@gmail.com|Huina]]&lt;br /&gt;
:::: Huina, there's no way to do what you want right now.  Interpolating between two images that are not created in Synfig is well beyond its scope right now.  However, what you could do is take an image and separate elements of the picture onto different layers (e.g. have a picture of an arm and another of the rest of the body) and you can move those around, stretch and rotate them.  (If you're familiar with the work of Terry Gilliam on Monty Python you'll know what I mean) I don't know how feasible it is to implement your request (I suspect some heavy lifting).  We'll keep it on the list, but don't hold your breath.  [[User:Pxegeek|Pxegeek]] 19:57, 24 November 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
:::: I think, you hardly find any other animation package  which allow you to do such things. You could use a special tools for this task, like xmorph (http://xmorph.sourceforge.net/). But to do the tween between two bitmap images you STILL need to set points. It's not tracing, but very similar. Anyway, result may be poor and I'd better suggest to use technique, described in Walking Cycle Tutorial or which the [[User:Pxegeek|Pxegeek]] meant. --[[User:Zelgadis|Zelgadis]] 02:08, 25 November 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
:::: There is a technique called &amp;quot;optical flow&amp;quot;.  It takes two input frames and calculates the movement of each individual pixel between the frames, allowing interpolation to be done. Here's an example: http://www.fxguide.com/article333.html.  It doesn't require setting of control points, but it has problems it's own set of problems: http://www.fxguide.com/article333.html. --[[User:Yoyobuae|Yoyobuae]] 13:32, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Auto-link option in [[Draw tool]] ===&lt;br /&gt;
&lt;br /&gt;
(4) so that you can draw a line, and have its endpoint automatically link to a duck - or if Auto-connect is off, you can get a line object linked to the end of another line object. / I missed this too, it even should be like that by default I think. [[User:Maxy|Maxy]] 13:22, 25 Apr 2006 (PDT)&lt;br /&gt;
&lt;br /&gt;
: Isn't this done already?  We don't have line objects, but blines are automatically linked to if auto-connect is on.  Am I missing something? -- [[User:Dooglus|dooglus]] 17:29, 27 September 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
::To clarify dooglus' comments - If you have an outline created by the draw tool highlighted in the layer dialog and the &amp;lt;b&amp;gt;auto-extend&amp;lt;/b&amp;gt; checkbox is checked, then you can continue drawing with the draw tool in that same layer.  Blines created with the Bline tool cannot be extended once a different tool or layer is selected.  [[User:Pxegeek|Pxegeek]] 23:46, 12 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
::: A line is a line - Synfig doesn't remember whether it was created with the Bline tool or the Draw tool - so you can extend blines created with the bline tool using the draw tool.  Just make sure the line is selected (so that its ducks are visible), not looped (so that it has end points to extend from), enable the draw tool, check 'auto extend' and start drawing at one of its end ducks. [[User:Dooglus|dooglus]] 05:47, 13 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
So this sounds like it is already done.  But on a related note, being able to open an existing bline in the bline tool to extend it would be useful. -- [[User:Dooglus|dooglus]] 04:51, 29 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Layer hide boolean parameter ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Panel]], and builds upon it as well, allowing the [[Layers Panel]] to dynamically unclutter. ''(This feature request is a refactoring of the [[Amount Parameter]])''&lt;br /&gt;
: With the addition of the [[Convert#Switch|Switch]] type conversion it is not needed this feature request. You can convert the Amount parameter to a Switch value and give 0 and 1 to the Linked OFF/ON values. --[[User:Genete|Genete]] 13:20, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Riding ducks ===&lt;br /&gt;
&lt;br /&gt;
(2) &amp;amp;mdash; Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.&lt;br /&gt;
:Already done in SVN.[[User:Genete|Genete]] 18:59, 5 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Image filmstrip import ===&lt;br /&gt;
&lt;br /&gt;
(2) &amp;amp;mdash; Allow import of a series of images (TGA, etc) as frames of an animation, on a layer. &amp;lt;br&amp;gt;&lt;br /&gt;
Response - 'lst' files of a list of images can be imported.  I've used this to develop a walk cycle.  See [[Walk_Cycle|Walk cycle]] for an example.  [[user:pxegeek|pxegeek]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Character Animation Tools ===&lt;br /&gt;
&lt;br /&gt;
I have seen some interesting methods for helping character design/animation in different 2d/3d software.  Hash's animation master has 'poses' which are extremes of a model, for example smiling and frowning, once you add these extremes ot a set you can use slider to create a pose that somewhere inbetween.  The real power of this is when you have serveral different poses on the same object, a face say,  you can easily come up with new facial expressions. Maybe something similar could be done with synfig using layers and groups, the implementation could something similar to Moho's switch layers. --[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)&lt;br /&gt;
: Have you read this tutorial? [[Reuse Animations]]. It is very close to the Switch layer of Moho/Anime Studio. Also You can change the Canvas parameter to any other canvas dynamically in the time line by clicking on it and selecting other exported canvas. Other option is convert the canvas to a Switch type and alternate between two different canvas.  --[[User:Genete|Genete]] 13:26, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== More Animation Tools ===&lt;br /&gt;
&lt;br /&gt;
[[New Animation Tools|Added here]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Improved User Experience for First Contact ===&lt;br /&gt;
* Single file download and installer (at least for Windows)&lt;br /&gt;
* Ability to draw the first object directly after starting the application (start with an empty document)&lt;br /&gt;
* Ability to animate the object directly after drawing the first object (new documents have a say 3 seconds timeline)&lt;br /&gt;
In my opinion this is crucial to attract potential users. Because if I see how easy it is to create my first animation I'm going to accept all the bugs and clumsyness. A good example is the Pencil animation software. --[[User:Dmd|Dmd]] 13:50, 26 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
: I've implemented #2 and #3 above in svn r1519 &amp;amp; 1520.  If no files are specified to be opened when running studio, it'll make a new one.  It won't pop up the canvas properties dialog when making new canvases by default.  And the default end time is 5s (3s is small enough to cause the time slider to show &amp;quot;1s 12f&amp;quot;, whereas 5s looks cleaner). -- [[User:Dooglus|dooglus]] 04:00, 29 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatic attach and manipulate a Vertex to a Bline ===&lt;br /&gt;
&lt;br /&gt;
Please see [[Inverse Duck Manipulation|this]] page to understand what we want. --[[User:Genete|Genete]] 12:43, 3 March 2008 (EST).&lt;br /&gt;
:Already done in SVN. [[User:Genete|Genete]] 19:00, 5 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Toggle visible ducks ===&lt;br /&gt;
(3) So pressing, say, tab while editing a Bline toggles which vertices/ducks are visible - so we can easily move the actual vertices around without having the view cluttered by tangeants (and also make it easier to select 'Loop' rather than 'Split Tangeants' when creating the thing.)&lt;br /&gt;
&lt;br /&gt;
Given that extra ducks such as the width ones listed above may be added, this might become more and more necessary. If too many different sets are added for toggling to be feasible, each visibility for each set can be hotkeyed.&lt;br /&gt;
&lt;br /&gt;
: Synfig already have hotkeys to toggle visibility of the ducks. See [[Keyboard_Shortcuts#Hotkeys_Visual_Guide]]. --[[User:Zelgadis|Zelgadis]] 00:39, 22 April 2008 (EDT)&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Doc:How_Do_I&amp;diff=7167</id>
		<title>Doc:How Do I</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Doc:How_Do_I&amp;diff=7167"/>
				<updated>2008-05-20T07:46:27Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Increase performance by optimizing during compilation time? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--Categories--&amp;gt;&lt;br /&gt;
[[Category:Tutorials]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Feel free to add your own questions here or [[Contact|contact]] us with them. Or put them on the [[Wiki Wish List]].&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Insert some text? ==&lt;br /&gt;
&lt;br /&gt;
With recent development versions, there is a text tool. If you are using 0.61.08 or earlier, use right click on your canvas and choose Layer &amp;gt; New &amp;gt; Other &amp;gt; Text.&lt;br /&gt;
&lt;br /&gt;
== Apply a gradient to an object instead of the entire canvas? ==&lt;br /&gt;
&lt;br /&gt;
# Create the region you want to fill with a gradient, and the gradient layer, if you haven't already.&lt;br /&gt;
# Make sure that the gradient layer is above the region layer in the [[Layers Panel]].&lt;br /&gt;
# Select both layers, right click, and select [[Encapsulate]].&lt;br /&gt;
# Expand the new [[Paste Canvas|Inline Canvas]] layer if it's not already, and select your gradient layer.&lt;br /&gt;
# In the [[Params Panel]] select the [[Blend Method]] parameter, and choose [[Blend Method#Onto|Onto]] from the drop-down menu.&lt;br /&gt;
&lt;br /&gt;
The gradient will clip to the visible area of the region below it inside the [[Paste Canvas|Inline Canvas]]. (and any other layers in that section).&lt;br /&gt;
&lt;br /&gt;
== Show or hide a layer, or fade the effect of a blur? ==&lt;br /&gt;
In the [[Params Panel]], look for an option labeled [[Amount Parameter|Amount]] - this controls how much of the blended result of the layer is composited with the blend of the layers beneath it.&lt;br /&gt;
&lt;br /&gt;
In other words, for a typical layer, this will 'fade it out'. For a [[Blur Layer]] set to &amp;quot;[[Blend Method#Straight|Straight]]&amp;quot;, this will fade ''between'' the blurred version and the unblurred version of the canvas. If you want it to become less blurry, adjust the [[Blur Layer#Size|Blur Layer's 'size' parameter]].&lt;br /&gt;
&lt;br /&gt;
== Fill an outline? ==&lt;br /&gt;
(Requested by [[User:Karlb|Karlb]])&lt;br /&gt;
&lt;br /&gt;
There are several options:&lt;br /&gt;
* The easiest way is to link a new region layer to the outline's shape.&lt;br /&gt;
*# Select the outline you want to fill.&lt;br /&gt;
*# In the Params Panel, right-click the Vertices parameter, select &amp;quot;Export&amp;quot;, enter a name for the shape, and hit return.  This will export the shape of the outline, making it visible in the Children dialog.&lt;br /&gt;
*# In the Children dialog, open the ValueBase Nodes tree and select the name you just saved the shape as.&lt;br /&gt;
*# From the [[Layer Menu]] (either context-click on the [[Layers Panel]] or use the [[Canvas Menu Caret]]) create a new [[Region Layer]] by selecting &amp;quot;New Layer -&amp;gt; Geometry -&amp;gt; Region&amp;quot;. Ensure that the created layer is selected.&lt;br /&gt;
*# In the parameter dialog, right-click the Vertices parameter and click &amp;quot;Connect&amp;quot;.&lt;br /&gt;
*# Now, if you don't need exported shape, you can unexport it: right click name of the shape in the Children dialog and click &amp;quot;Unexport&amp;quot;.&lt;br /&gt;
* Similar to the above, but using a different method:&lt;br /&gt;
*# Create a new region layer as above, and leave it selected.&lt;br /&gt;
*# Don't make any changes to the outline layer, which you want to fill! (see the Tier 5 on the [[Linking]] page for details).&lt;br /&gt;
*# Select both layers in the [[Layers Panel]] This will display only the parameters shared by both layers in the [[Params Panel]].&lt;br /&gt;
*# Context-click on the [[Vertices Parameter]], and select [[Linking|Link]].&lt;br /&gt;
*# The [[Region Layer]] will snap to the shape of the [[Outline Layer]].&lt;br /&gt;
* When you create an [[Outline Layer|outline]] with the [[Bline Tool]] that you intend to be a filled area as well, make sure you select the Fill checkbox in the [[Bline Tool#Options|tool options dialog]]. Obviously, this doesn't help much if you realise later that you needed a fill here.&lt;br /&gt;
* If you are using the [[draw tool]], there is a button at the bottom of the [[draw tool#Options|tool options dialog]] labeled &amp;quot;Fill Last Stroke&amp;quot;, which creates a new [[Region Layer]] and links its shape to the previously drawn outline. Unfortunately, it doesn't work as of Synfig Studio v0.61.04.  It has been fixed in the current SVN version of the code.&lt;br /&gt;
* Create a [[Region Layer|region]] with the same number of ducks, and manually link each duck. If you want a region that depends on multiple outline layers, this is really your only choice for now.&lt;br /&gt;
* Use the draw tool, select only the outline to fill, draw a stroke roughly following the outline and make sure you're holding the Control key when you left go of the mouse button at the end of the stroke.  This doesn't work 100% right at the moment.&lt;br /&gt;
&lt;br /&gt;
== Dock windows together? ==&lt;br /&gt;
&lt;br /&gt;
*To dock (join) separate windows into one you must drag the tab ''icons'' for each of the tools into another window. &lt;br /&gt;
*You can create subdivisions inside the windows by dragging the icons into the side tabs (located around the edges, the look like rectangles). &lt;br /&gt;
*Tool tabs inside the window can be arranged by dragging them on top of one another, therefore changing the order.&lt;br /&gt;
*''How Do I min/maximize all Synfig windows on a Windows pc''? There must be an easy way/tool to do this?&lt;br /&gt;
&lt;br /&gt;
== Use an external bitmap? ==&lt;br /&gt;
&lt;br /&gt;
* In the image menu (&amp;gt;) choose file--&amp;gt;import. PNG with alpha channel works fine.&lt;br /&gt;
* To animate it without accidental stretching, right-click on the layer and choose encapsulate. You can then animate the position of the new &amp;quot;Inline Canvas&amp;quot; layer instead of the bbox.&lt;br /&gt;
&lt;br /&gt;
== Use an external Vector? ==&lt;br /&gt;
&lt;br /&gt;
Synfig doesn't yet support vector import because no-one has written an import process yet. You can use the Svg2synfig [[Converters|converter]], or import it as a bitmap and trace over it in synfig. If you want to implement vector import we would gladly accept your patch.&lt;br /&gt;
&lt;br /&gt;
== Close a bline? ==&lt;br /&gt;
&lt;br /&gt;
* Right click on the starting point and then click on loop bline.&lt;br /&gt;
&lt;br /&gt;
Note: It doesn't work unless the initial point has a tangent - ie the first segment is curved. But you can hide tangent ducks (Alt+3, or &amp;quot;Caret Menu &amp;gt; View &amp;gt; Show/Hide Ducks &amp;gt; Show tangent ducks&amp;quot;) and process as described. Don't forget to press (Alt+3) after that to show tangent ducks again.&lt;br /&gt;
&lt;br /&gt;
== How do I transform encapsulated objects? ==&lt;br /&gt;
&lt;br /&gt;
* Right click on the Encapsulated object in the Layer dialog and choose &amp;quot;select all child layers&amp;quot;. Then you select the ducks you want to transform (usually just all of them, like for rotating the object), and the rotate or scale tool and do the work.&lt;br /&gt;
&lt;br /&gt;
== Make objects go behind each other, without moving layers? ==&lt;br /&gt;
&lt;br /&gt;
You'll notice each layer you make has a number in the z depth column in the Layers Panel. Say you have 3 layers, they will be numbered 2 (lowest, e.g. a square) 1 (eg a circle) 0 (highest, the default, e.g. a line). In order to make layer 1, the circle, pass behind layer 2, the square, change its z depth to be 3 or more. The z depth of the circle needs to be greater than 2 in order to be behind the square. To make the square on top of everything, you'd change its z depth to -1 or less. &lt;br /&gt;
&lt;br /&gt;
Positive numbers on the z axis go into the screen, and negative numbers go out of the screen, towards the viewer.  &lt;br /&gt;
&lt;br /&gt;
It is possible to animate this effect, but each layer is discrete. They seem to go from 0 to 0.9999.&lt;br /&gt;
&lt;br /&gt;
In addition, objects in encapsulated layers can only go behind other objects in the same encapsulated layer. However an encapsulated layer can go behind another encapsulated layer.&lt;br /&gt;
&lt;br /&gt;
== Copy a complex convert combination between parameters of different layers? ==&lt;br /&gt;
&lt;br /&gt;
For example: you want to copy a complicated [[Convert|conversion]] type that you have in one parameter from a layer, to other parameter (maybe not a root parameter, but a sub-parameter) of other layer. If you [[Export|export]] the complicated conversion type from the original layer and then go to the other layer and select [[Connect]] (right click and the exported and the parameter both selected) then you have the parameter form the second layer to be exactly the same than the original one. But there is a drawback: if you modify one of the sub-parameters in the complicated conversion type (e.g. you change the value of one of them) then automatically the same sub-parameter of the other layer is changed.&lt;br /&gt;
&lt;br /&gt;
How can you copy the conversion but allow modify the sub-parameters independently on each layer? &lt;br /&gt;
&lt;br /&gt;
Once you have achieved the complex conversion type in the original layer, &amp;lt;u&amp;gt;don't export the root parameter!&amp;lt;/u&amp;gt; If you have done yet [[Export|unexport]] it. (Why?. You will understand it later.) Now duplicate the original layer. Then you should obtain the same layer with the same conversion type placed at the same parameter (but not exported). NOW export the parameter from the duplicated layer. Then go to the (sub) parameter of the layer where you want to copy the complex conversion type and Connect it to the just exported parameter form the duplicated layer. Now delete the duplicated layer (!). Then the exported [[ValueNode]] still undeleted and the layer where you wanted to copy the complex convert type have a (sub) parameter connected to it. You can [[Export|unexport]] the ValueNode or not. It is up to you. But notice that the conversion type is already copied into other (sub) parameter of other layer and they are independent as well as you can change one of them (by modifying the sub-parameters) and the other remains untouched.&lt;br /&gt;
&lt;br /&gt;
== Make an existing animation run at half speed? ==&lt;br /&gt;
&lt;br /&gt;
If you have an animation that runs from 0s to 10s and you want it to run at half speed from 0s to 20s, how can you do that?&lt;br /&gt;
&lt;br /&gt;
* Either: encapsulate it, and use the 'time offset' parameter in the encapsulation layer to slow it down:&lt;br /&gt;
** Right-click 'time offset' in the encapsulation layer, convert&amp;gt;linear, rate -0.5 offset 0.  That means offset the time by -0.5 seconds per second - or in other words, run at half speed&lt;br /&gt;
** Or, putting waypoints on the 'time offset' param would work too: 0 at 0s and -10 at 20s.  (The choice between using a linear convert and valuenodes is entirely up to you.  They both achieve the same result in this simple case).&lt;br /&gt;
&lt;br /&gt;
* Or: use a [[Time Loop Layer]].  The first method seems better and more intuitive in this case, but there are ways of getting the same effect from the Time Loop layer.  Perhaps the Time Loop layer is better if the animation doesn't run from 0s, but from some other time.  Anyway: put a Time Loop layer over the layers you wish to slow down, and:&lt;br /&gt;
** Either: set duration to 0, local time to 0, convert-&amp;gt;linear the link time and set rate to 0.5 - this slows the animation down *to* 50% of its original speed;  use bigger rates to slow it down less&lt;br /&gt;
** Or: set duration to 1h (*), link time to 0, convert-&amp;gt;linear the local time and set rate to 0.5 - this slows the animation down *by* 50%; use bigger rates to slow it down more&lt;br /&gt;
(*) if your animation is longer than 1h then set this parameter to EOT (End Of Time) what is the same as Infinite (INF) for a real number but for a time parameter.&lt;br /&gt;
&lt;br /&gt;
== Draw a rectangle with a given width and height? ==&lt;br /&gt;
&lt;br /&gt;
I was asked on IRC how to specify the width and height of a rectangle, rather than having to specify the position of two opposite corners.  Here's how:&lt;br /&gt;
&lt;br /&gt;
* draw a rectangle&lt;br /&gt;
* go to the [[Params Panel]]&lt;br /&gt;
* right-click the 'point 1' parameter and [[Export]]&lt;br /&gt;
* give it a name, &amp;quot;p1&amp;quot; say&lt;br /&gt;
* right-click the 'point 2' parameter and [[Convert]] to [[Convert#Add|Add]]&lt;br /&gt;
* (that's saying that rather than specifying the absolute position of the other point, you want synfig to calculate it for you)&lt;br /&gt;
* (it will make 2 new sub-parameters for 'point 2', and the value used for point 2 will be their sum so we want to tell it to use 'point 1' and your (width,height))&lt;br /&gt;
* open up the sub-parameters of 'point 2' by clicking the triangle to its left&lt;br /&gt;
* go to the [[Children Panel]], open up the values and select the one you exported earlier (p1)&lt;br /&gt;
* right-click the &amp;quot;LHS&amp;quot; parameter in the parameters dialog and [[Connect]] it&lt;br /&gt;
* then enter the width and height you want in the 'RHS' parameter&lt;br /&gt;
&lt;br /&gt;
== Make linked BLine vertices not affected by Rotate layer? ==&lt;br /&gt;
Look at the http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-02-07.log &lt;br /&gt;
See also: [[Convert]].&lt;br /&gt;
&lt;br /&gt;
== Create dashed outlines? ==&lt;br /&gt;
&lt;br /&gt;
If you want to make simple dashed outlines the faster way is proceed like this:&lt;br /&gt;
&lt;br /&gt;
* Create a Curve Gradient and an Outline over the same [[Bline]] using the [[Bline Tool]] options. Check both Outline and Gradient at the [[Tool Options Panel]].&lt;br /&gt;
* Raise up the gradient layer (it is created below the [[Outline Layer]]).&lt;br /&gt;
* Modify the gradient [[Blend Method]] parameter to be Straight Onto. That would render the gradient onto the outline width. Also it wouldn't render the outline, so transparent portions of the gradient are transparent.&lt;br /&gt;
* Check the 'Perpendicular' parameter of the Curve Gradient Layer.&lt;br /&gt;
* [[Convert]] the Gradient Parameter of the Curve Gradient Layer to be one of those types: Stripes or Repeat Gradient.&lt;br /&gt;
* Modify the properties of the sub parameters to achieve the desired effect.&lt;br /&gt;
&lt;br /&gt;
== Render to AVI with higher quality? ==&lt;br /&gt;
&lt;br /&gt;
=== Using raw video ===&lt;br /&gt;
The module used by Synfig to render AVI files is ffmpeg. For the moment there is not interface to control ffmpeg options so you render with a fixed bitrate and quality. If you want the maximum quality in your AVI file, follow these steps:&lt;br /&gt;
&lt;br /&gt;
* Render your animation to yuv420p format. To do that select that target at the drop down list of the render dialog and add the &amp;quot;.yuv&amp;quot; extension to your animation name (without quotes).&lt;br /&gt;
* Once rendered (it would produce a huge size yuv file) you can quickly convert it to AVI using this command:&lt;br /&gt;
&lt;br /&gt;
 ffmpeg -i animation.yuv -sameq animation.avi&lt;br /&gt;
&lt;br /&gt;
Change the animation file name to your one.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Rendering trough png sequence. ===&lt;br /&gt;
Render your sif to png sequence &lt;br /&gt;
 mkdir render&lt;br /&gt;
 synfig my_animation.sifz -o render/frame.png&lt;br /&gt;
Then convert it to movie with ffmpeg&lt;br /&gt;
 ffmpeg -r &amp;lt;frame rate&amp;gt; -i render/frame.%04d.png &amp;lt;more settings from ffmpeg's manual&amp;gt; my_animation.mov&lt;br /&gt;
If you need nice open source format without any tweaks you may try ffmpeg2theora:&lt;br /&gt;
 ffmpeg2theora render/frame.%04d.png --inputfps &amp;lt;frame rate&amp;gt; -o my_animation.ogg&lt;br /&gt;
png takes less disk space then yuv.&lt;br /&gt;
--[[User:AkhIL|AkhIL]] 21:38, 9 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
==Increase performance by optimizing during compilation time? ==&lt;br /&gt;
&lt;br /&gt;
I would like to know what parameters do I need to apply to configure to improve performance. [[User:Genete|Genete]] 11:04, 9 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
To optimize program you should set two environment variables&lt;br /&gt;
 export CFLAGS=&amp;quot;&amp;quot;&lt;br /&gt;
 export CXXFLAGS=$CFLAGS&lt;br /&gt;
&lt;br /&gt;
First flag will be &amp;quot;-O3&amp;quot; (ow three). &amp;quot;-02&amp;quot; is normal optimization. &amp;quot;-03&amp;quot; is hard optimisation.&lt;br /&gt;
&lt;br /&gt;
Now you should get info about your CPU&lt;br /&gt;
 cat /proc/cpuinfo&lt;br /&gt;
&lt;br /&gt;
find your cpu model name&lt;br /&gt;
&lt;br /&gt;
now go to man gcc and searc &amp;quot;-mtune&amp;quot;&lt;br /&gt;
&lt;br /&gt;
find your cpu and add &amp;quot;-mtune=your-cpu -march=your-cpu&amp;quot; to CFLAGS. &lt;br /&gt;
&lt;br /&gt;
Then look at flags from /proc/cpuinfo and search it in gcc manual&lt;br /&gt;
For example I have 3dnow. So I can find &amp;quot;-m3dnow&amp;quot;. For sse I can find &amp;quot;-msse&amp;quot; and &amp;quot;-mfpmath=sse&amp;quot; (can make program unstable). &lt;br /&gt;
&lt;br /&gt;
Finaly you may add &amp;quot;-ffast-math&amp;quot; to disable math checks. But it can make program unstable.&lt;br /&gt;
&lt;br /&gt;
For my AthlonXP I'm using this flags:&lt;br /&gt;
 export CFLAGS=&amp;quot;-O3 -pipe -mtune=athlon-xp -march=athlon-xp -mmmx -msse -m3dnow -mfpmath=sse -ffast-math -funsigned-char -fno-strict-aliasing&amp;quot;&lt;br /&gt;
 export CXXFLAGS=$CFLAGS&lt;br /&gt;
--[[User:AkhIL|AkhIL]] 12:05, 9 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
For my Pentium3 i use the line:&lt;br /&gt;
export CFLAGS=&amp;quot;-O3 -pipe -mtune=pentium3 -march=pentium3 -msse -mfpmath=sse -funsigned-char -fno-strict-aliasing&amp;quot;&lt;br /&gt;
 export CXXFLAGS=$CFLAGS&lt;br /&gt;
--[[User:SvH|SvH]] 03:46, 20 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
== Granted Wishes ==&lt;br /&gt;
&lt;br /&gt;
=== MNG target filetype ===&lt;br /&gt;
&lt;br /&gt;
The ability to save as/in the Free/Open MNG (.mng) format [http://libpng.org/pub/mng/]&lt;br /&gt;
&lt;br /&gt;
A partial implementation was committed in SVN r470.&lt;br /&gt;
&lt;br /&gt;
It was implemented in svn 986. See [[Render options]]. --[[User:Genete|Genete]] 13:12, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== Optionally display RGB in Hex in Color dialog ===&lt;br /&gt;
&lt;br /&gt;
(3) When colors are quoted as 3 bytes of hexadecimal, you have to convert them to decimal, divide by 255, multiply by 100 to get a number to type into the dialog box.  It's painful to match color schemes for example, with the [http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines Tango Icon Theme style guidelines].  [[User:pxegeek|PXEGeek]] 3/16/07&lt;br /&gt;
&lt;br /&gt;
: Added in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=40dda9d27b5249ee32f62d84c819ff569f078929 svn r354].  You can type 3 or 6 digit hex codes and hit return to use.  3 digit code 36a gives colour 3366aa (each digit is duplicated) -- [[User:Dooglus|dooglus]] 3/18/07&lt;br /&gt;
&lt;br /&gt;
:: Many thanks - already used many times! PXEGeek.&lt;br /&gt;
&lt;br /&gt;
::: Did you notice that you can use single digit codes too?  '5' gives 555555 for instance, giving you 16 equally spaces shades of black through white. -- [[User:Dooglus|dooglus]] 17:51, 25 September 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== Restore Default Layout ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.&lt;br /&gt;
-&amp;gt; I'd like to second this one - especially with the bug where dialog boxes sometime shrink to nothing or offscreen, and no amount of maximizing or minimizing restores them.  The only solution is to kill the windows, and none of the combo options in the dialog menu match the default configuration.  4/4/07 PXEGeek&lt;br /&gt;
&lt;br /&gt;
: Implemented in [http://kibi.dyndns.org:8083/~dooglus/gitweb.pl?p=synfig;a=commitdiff;h=036306f3c2c265a604971728d50fcce258766552 svn r757] -- [[User:Dooglus|dooglus]] 17:48, 25 September 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== General outline / Polygon-based Outline / &amp;quot;Set Tangents to Zero&amp;quot; button ===&lt;br /&gt;
(3.5) I'm no artist, thus my primary form of art is stick figures, not to mention, many interesting animations are done in stick-figure style. Stick figures must be perfectly straight to get the effect across, so when I'm making an outline using B-Curves, it is too time consuming to set the tangents to 0 each time. Similarly, outlines of other shapes like squares, circles and so forth would be very useful. Whichever of the above is easiest, please implement right away. --[[User:Dragontamer|Dragontamer]] 02:35, 19 November 2007 (EST)&lt;br /&gt;
: For perfectly straight lines, click without moving the mouse.  You will get a single point with no tangents.  Outline shapes would require some development, particularly with some thought given to backward compatibility.  A workaround you might consider is to create a duplicate shape with a different color and make the top one slightly smaller, so the outline of the one below shows.  [[User:Pxegeek|Pxegeek]] 21:58, 19 November 2007 (EST)&lt;br /&gt;
:: Well, in general, whenever I click on a point to edit it (say, to make it move somewhere in animation mode), there is a decent chance that I click on a tangent instead. Then, if I want to right click the point itself, I usually right click the tangent marker instead. It isn't that big a deal, but simplicity at the cost of power generally is a good thing, especially when it will save a few mouse clicks. &lt;br /&gt;
:: As for the outlines, yeah, I've tried that and it is a decent solution for now, although it is no replacement for a real outline. I am going to also experiment with a clamp to see if I can make the center of the shape have 100% alpha... but I don't have synfig on the computer I'm on right now. Thanks for the tips Pxegeek. --[[User:Dragontamer|Dragontamer]] 01:58, 27 November 2007 (EST)&lt;br /&gt;
::: You can press Alt+3 to hide tangent ducks. --[[User:Zelgadis|Zelgadis]] 09:27, 27 November 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Copy &amp;amp; Paste/Image Importing ===&lt;br /&gt;
&lt;br /&gt;
(4) I sometimes make graphics in other programs, or use clipart and other images. Would it be possible for Synfig to be able to import images and/or copy and paste them?--Khlieeq 2007-07-19&lt;br /&gt;
Well, it doesn't support Copy &amp;amp; paste from the clipboard, but you can import images using &amp;quot;New Layer -&amp;gt; Other -&amp;gt; Import&amp;quot;.  This will create an Import layer, for which you can then edit the properties to point to the file containing your image.  PXEGeek.  2007-07-19&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Recursive Waypoint Manipulation ===&lt;br /&gt;
&lt;br /&gt;
(4) it is really tiresome to revert changes to waypoints created by manipulating tangent/position ducks or change their interpolation functions. making it possible to right-click-modify the waypoint shown for objects that have some waypoint in a referenced sub-object would be great! -- timonator 2007-06-01&lt;br /&gt;
:You can do it in two ways: changing the interpolation method of the waypoint of paste canvas or editing the keyframe properties. The first allow to modify the waypoints interpolation method for all the waypoints of all the parameters of all the layers that are inside the paste canvas layer. You can right click on the left or right part of the waypoint to edit by a context menu the left or the right interpolation method of the waipoints. The second method would add and modify all the parameters that have any waypoint in the animation. See [[Keyframe]] for more detail. --[[User:Genete|Genete]] 13:10, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Tweening for images developed in other imaging programs ===&lt;br /&gt;
&lt;br /&gt;
It's obvious I am a beginner at image movement, but morphing is not enough: movement across the page is needed.  Thanks for listening. [[User:Comwell@bellsouth.net|Comwell]]&amp;lt;br&amp;gt;&lt;br /&gt;
Imported images can be moved across the page.  They can also be scaled, rotated and deformed.  Was there a specific example you had in mind?  [[User:Pxegeek|pxegeek]]&amp;lt;br&amp;gt;&lt;br /&gt;
:I also would like a way to tween images that have been drawn in other programs. I've had trouble drawing with Bline tool and the drawing tool in Synfig, and I'd rather just draw with a paint brush (like the one in Photoshop). Another problem I have is that Synfig tends to shut down on me every 20 minutes or so, and it's really frustrating even with the auto recover feature, because my sketches disappear. It'd be nice if I'm able to draw all of the keyframes in Photoshop or another image program and import it to Synfig so that Synfig can tween and animate them. Thank you. [[User:xychefoo@gmail.com|Huina]]&lt;br /&gt;
::You CAN use images, drawn in other programs. Just select &amp;quot;File-&amp;gt;Import&amp;quot; from [[Canvas Menu Caret|canvas menu]] --[[User:Zelgadis|Zelgadis]] 01:39, 24 November 2007 (EST)&lt;br /&gt;
:::But how do you animate using images from other sources? I tried to make 2 keyframes with 2 different images, and it doesn't animate. It just stays as 1 picture for the entire render. The closest thing I saw to importing images from another source into Synfig and having it animate is the Walking Cycle Tutorial, but I would still have to trace the images to make it animate. As I said earlier, I'm not entirely fond of using the draw/Bline tool.  [[User:xychefoo@gmail.com|Huina]]&lt;br /&gt;
:::: Huina, there's no way to do what you want right now.  Interpolating between two images that are not created in Synfig is well beyond its scope right now.  However, what you could do is take an image and separate elements of the picture onto different layers (e.g. have a picture of an arm and another of the rest of the body) and you can move those around, stretch and rotate them.  (If you're familiar with the work of Terry Gilliam on Monty Python you'll know what I mean) I don't know how feasible it is to implement your request (I suspect some heavy lifting).  We'll keep it on the list, but don't hold your breath.  [[User:Pxegeek|Pxegeek]] 19:57, 24 November 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
:::: I think, you hardly find any other animation package  which allow you to do such things. You could use a special tools for this task, like xmorph (http://xmorph.sourceforge.net/). But to do the tween between two bitmap images you STILL need to set points. It's not tracing, but very similar. Anyway, result may be poor and I'd better suggest to use technique, described in Walking Cycle Tutorial or which the [[User:Pxegeek|Pxegeek]] meant. --[[User:Zelgadis|Zelgadis]] 02:08, 25 November 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
:::: There is a technique called &amp;quot;optical flow&amp;quot;.  It takes two input frames and calculates the movement of each individual pixel between the frames, allowing interpolation to be done. Here's an example: http://www.fxguide.com/article333.html.  It doesn't require setting of control points, but it has problems it's own set of problems: http://www.fxguide.com/article333.html. --[[User:Yoyobuae|Yoyobuae]] 13:32, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Auto-link option in [[Draw tool]] ===&lt;br /&gt;
&lt;br /&gt;
(4) so that you can draw a line, and have its endpoint automatically link to a duck - or if Auto-connect is off, you can get a line object linked to the end of another line object. / I missed this too, it even should be like that by default I think. [[User:Maxy|Maxy]] 13:22, 25 Apr 2006 (PDT)&lt;br /&gt;
&lt;br /&gt;
: Isn't this done already?  We don't have line objects, but blines are automatically linked to if auto-connect is on.  Am I missing something? -- [[User:Dooglus|dooglus]] 17:29, 27 September 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
::To clarify dooglus' comments - If you have an outline created by the draw tool highlighted in the layer dialog and the &amp;lt;b&amp;gt;auto-extend&amp;lt;/b&amp;gt; checkbox is checked, then you can continue drawing with the draw tool in that same layer.  Blines created with the Bline tool cannot be extended once a different tool or layer is selected.  [[User:Pxegeek|Pxegeek]] 23:46, 12 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
::: A line is a line - Synfig doesn't remember whether it was created with the Bline tool or the Draw tool - so you can extend blines created with the bline tool using the draw tool.  Just make sure the line is selected (so that its ducks are visible), not looped (so that it has end points to extend from), enable the draw tool, check 'auto extend' and start drawing at one of its end ducks. [[User:Dooglus|dooglus]] 05:47, 13 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
So this sounds like it is already done.  But on a related note, being able to open an existing bline in the bline tool to extend it would be useful. -- [[User:Dooglus|dooglus]] 04:51, 29 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Layer hide boolean parameter ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Panel]], and builds upon it as well, allowing the [[Layers Panel]] to dynamically unclutter. ''(This feature request is a refactoring of the [[Amount Parameter]])''&lt;br /&gt;
: With the addition of the [[Convert#Switch|Switch]] type conversion it is not needed this feature request. You can convert the Amount parameter to a Switch value and give 0 and 1 to the Linked OFF/ON values. --[[User:Genete|Genete]] 13:20, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Riding ducks ===&lt;br /&gt;
&lt;br /&gt;
(2) &amp;amp;mdash; Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.&lt;br /&gt;
:Already done in SVN.[[User:Genete|Genete]] 18:59, 5 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Image filmstrip import ===&lt;br /&gt;
&lt;br /&gt;
(2) &amp;amp;mdash; Allow import of a series of images (TGA, etc) as frames of an animation, on a layer. &amp;lt;br&amp;gt;&lt;br /&gt;
Response - 'lst' files of a list of images can be imported.  I've used this to develop a walk cycle.  See [[Walk_Cycle|Walk cycle]] for an example.  [[user:pxegeek|pxegeek]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Character Animation Tools ===&lt;br /&gt;
&lt;br /&gt;
I have seen some interesting methods for helping character design/animation in different 2d/3d software.  Hash's animation master has 'poses' which are extremes of a model, for example smiling and frowning, once you add these extremes ot a set you can use slider to create a pose that somewhere inbetween.  The real power of this is when you have serveral different poses on the same object, a face say,  you can easily come up with new facial expressions. Maybe something similar could be done with synfig using layers and groups, the implementation could something similar to Moho's switch layers. --[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)&lt;br /&gt;
: Have you read this tutorial? [[Reuse Animations]]. It is very close to the Switch layer of Moho/Anime Studio. Also You can change the Canvas parameter to any other canvas dynamically in the time line by clicking on it and selecting other exported canvas. Other option is convert the canvas to a Switch type and alternate between two different canvas.  --[[User:Genete|Genete]] 13:26, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== More Animation Tools ===&lt;br /&gt;
&lt;br /&gt;
[[New Animation Tools|Added here]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Improved User Experience for First Contact ===&lt;br /&gt;
* Single file download and installer (at least for Windows)&lt;br /&gt;
* Ability to draw the first object directly after starting the application (start with an empty document)&lt;br /&gt;
* Ability to animate the object directly after drawing the first object (new documents have a say 3 seconds timeline)&lt;br /&gt;
In my opinion this is crucial to attract potential users. Because if I see how easy it is to create my first animation I'm going to accept all the bugs and clumsyness. A good example is the Pencil animation software. --[[User:Dmd|Dmd]] 13:50, 26 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
: I've implemented #2 and #3 above in svn r1519 &amp;amp; 1520.  If no files are specified to be opened when running studio, it'll make a new one.  It won't pop up the canvas properties dialog when making new canvases by default.  And the default end time is 5s (3s is small enough to cause the time slider to show &amp;quot;1s 12f&amp;quot;, whereas 5s looks cleaner). -- [[User:Dooglus|dooglus]] 04:00, 29 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatic attach and manipulate a Vertex to a Bline ===&lt;br /&gt;
&lt;br /&gt;
Please see [[Inverse Duck Manipulation|this]] page to understand what we want. --[[User:Genete|Genete]] 12:43, 3 March 2008 (EST).&lt;br /&gt;
:Already done in SVN. [[User:Genete|Genete]] 19:00, 5 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Toggle visible ducks ===&lt;br /&gt;
(3) So pressing, say, tab while editing a Bline toggles which vertices/ducks are visible - so we can easily move the actual vertices around without having the view cluttered by tangeants (and also make it easier to select 'Loop' rather than 'Split Tangeants' when creating the thing.)&lt;br /&gt;
&lt;br /&gt;
Given that extra ducks such as the width ones listed above may be added, this might become more and more necessary. If too many different sets are added for toggling to be feasible, each visibility for each set can be hotkeyed.&lt;br /&gt;
&lt;br /&gt;
: Synfig already have hotkeys to toggle visibility of the ducks. See [[Keyboard_Shortcuts#Hotkeys_Visual_Guide]]. --[[User:Zelgadis|Zelgadis]] 00:39, 22 April 2008 (EDT)&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Dev:Wish_list&amp;diff=7157</id>
		<title>Dev:Wish list</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Dev:Wish_list&amp;diff=7157"/>
				<updated>2008-05-14T05:37:56Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Vector fill bucket */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''''Warning''''': We need more people working on the code if we are going to be able to achieve all the feature requests.&lt;br /&gt;
&lt;br /&gt;
Got a great idea for a new feature? Just add it here, or on the [http://sourceforge.net/tracker/?group_id=144022&amp;amp;atid=757419 feature requests tracker]. Before you do, please check the [http://svn.voria.com/code/ETL/trunk/TODO etl], [http://svn.voria.com/code/synfig-core/trunk/TODO synfig] and [http://svn.voria.com/code/synfig-studio/trunk/TODO synfigstudio] TODO files for similar ideas. Please add a rating of how essential this feature is to your workflow according to the following scale:&lt;br /&gt;
&lt;br /&gt;
#&amp;quot;Well, it might be nifty. To someone.&amp;quot;&lt;br /&gt;
#&amp;quot;I probably would make use this&amp;quot;&lt;br /&gt;
#&amp;quot;It's not essential, but I'd really like to have this at my disposal.&amp;quot;&lt;br /&gt;
#&amp;quot;Synfig would be soooo much better with this change&amp;quot;&lt;br /&gt;
#&amp;quot;I can't/won't use Synfig without it!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== Wishes ==&lt;br /&gt;
&lt;br /&gt;
=== get_color method in text and radial blur ===&lt;br /&gt;
&lt;br /&gt;
[5] Without get_color method distorion produces artifacts &lt;br /&gt;
[http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1831355&amp;amp;group_id=144022&amp;amp;atid=757416 bug  1831355]. So I would like to get this problem fixed before doing something else. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== Full functional of group dialog ===&lt;br /&gt;
&lt;br /&gt;
[5] Group dialog is broken now [http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1796833&amp;amp;group_id=144022&amp;amp;atid=757416 bug 1796833]. So we should get old features work right before making new one. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== import/export .swf files ===&lt;br /&gt;
&lt;br /&gt;
very important productivity feature&lt;br /&gt;
&lt;br /&gt;
=== import/export .svg frames sequence, and/or .svg animations ===&lt;br /&gt;
&lt;br /&gt;
very important productivity feature&lt;br /&gt;
&lt;br /&gt;
=== a realtime .sif synchronized text window ===&lt;br /&gt;
&lt;br /&gt;
just like the xml editor of Inkscape, or the html editor in Dreamweaver (this is hugelly useful for productivity)&lt;br /&gt;
&lt;br /&gt;
I thinks scripting API can be implement in this way. For example you make XML DOM like implementation for python which alows to change DOM tree from python code and see chenges in canvas. By this way you can implement import/export scripts. Automation scripts. And a lot of different things. Even synchronization of animation between blender and synfig. --[[User:AkhIL|AkhIL]] 23:10, 26 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== choosing colour from gimp/inkscape palettes ===&lt;br /&gt;
&lt;br /&gt;
very useful when you need some colour comformity of what you're doing &lt;br /&gt;
&lt;br /&gt;
=== Good high-level documentation of the source code ===&lt;br /&gt;
&lt;br /&gt;
(2) It'd be nice if a newbie could quickly navigate around the source code. The best thing to do would be to add top-level comments in each file, explaining what that file does, a README.TXT in each directory, explaining what's in that directory. This would be pretty fast and easy to do, and make it much easier for new programmers to join. &lt;br /&gt;
&lt;br /&gt;
Time permitting, it would also be good to document on a high level what the data structures are, but that's harder, since those tend to evolve, and it is often difficult to keep in sync. It would also be useful to document what individual functions do (just a one-liner high-level description), but that also takes more time.&lt;br /&gt;
: There is a page link in the wiki that connect to the [http://www.synfig.com/doc Synfig API Documentation]. I think this link should be highlighted to be more accessible for newbies contributors and mature developers (the link was found [[Releases/DeveloperPreview#Support | here]]). --[[User:Genete|Genete]] 10:02, 11 December 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Mathematical functions to animate ===&lt;br /&gt;
(2/4) If you want to make a waving flag, it would be handful a sine function, tuned with random correctors, for example. &lt;br /&gt;
: -This should generate waypoints each 1, 2, 4 frames or any other step at artist's wish.&lt;br /&gt;
: -When applying a function you can add it to current values, add it to 1st frame values or simply override old values. Perhaps other options (such multiplication) would be fine, too. Something like texture editor in [http://www.artofillusion.org Art of Illusion], perhaps.&lt;br /&gt;
Perhaps it would be useful reusing the [http://www.gnu.org/software/octave/ Octave] source code to parse mathematical expressions.&lt;br /&gt;
I have rated this wish with a '2' because undoubtly many users will not be familiar to mathematical concepts, but for those who will be, I'd rate it with a 4. It would be possible to make a ball describing a parabolic moving in no time.&lt;br /&gt;
[[User:ajotatxe|ajotatxe]] 20 November 2007&lt;br /&gt;
: dooglus can probably chime in better than I here (see his example of balls on mathematical paths at http://uk.youtube.com/watch?v=YTpSfUthuVE ), but I believe that this is already possible.  Synfig does support a variety of mathematical transforms for parameters, although the way you do this is by no means intuitive.  (You might also want to check out the preambletaffy.sifz example for an easier approach to a waving flag. I know you were just using that as an example, but for the record...) [[User:Pxegeek|Pxegeek]] 00:58, 21 November 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
: I'd also rate it with a (4) (and updated the rating accordingly), not for this special case, but to make many workarounds much easier.  Simulating [Parabolic Shot|free fall], for example, would be a lot easier with real formulas.  I don't know, though how easy it will be to implement, maybe waiting for a scripting interface to be implemented is better than hacking this feature in an ad-hoc manner.  --[[User:Rubikcube|Rubikcube]] 16:38, 29 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Warning about editing bizarre things in animate editing mode ===&lt;br /&gt;
(3.5) It seems to have little sense animate certain things like Blend Method or Type of Feather. It would be very nice that the program asked comfirmation if you change these attributes in animate editing mode. If you do want to, you would have three options: &amp;quot;Yes, never ask&amp;quot;, &amp;quot;Yes, never ask for this attribute&amp;quot;, &amp;quot;No&amp;quot;. I guess that internally, this attributes has integer type (or something like that) and the attributes that you normally want to animate, float type, so I think that this feature is relatively easy to implement. My English is not very good, so please feel free to fix this post.&lt;br /&gt;
[[User:ajotatxe|ajotatxe]] 20 November 2007&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bones with FK &amp;amp; IK + grouping of objects into folders ===&lt;br /&gt;
&lt;br /&gt;
(1) Bones cane move specific vector assigned to them or the bones can have envelopes that move the vectors within their field of influence, much Like Anime Studio/Moho does. It's quite a time saving process of animating. Objects created can be saved into separate groups or folders using the same system as Anime Studio/Moho -Shadowphoenix 27/8/2007&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Animated sketch ===&lt;br /&gt;
&lt;br /&gt;
(1) it would be great, if the tool Sketch was animatable (for example, in a form of a special sketch-layer). --Zelgadis 2007-06-14&lt;br /&gt;
&lt;br /&gt;
=== Duck for Amount value in Zoom layer ===&lt;br /&gt;
&lt;br /&gt;
(2) It would be nice if Amount value in Zoom layer was controlled by additional duck. --[[User:Zelgadis|Zelgadis]] 02:49, 29 December 2007 (EST)&lt;br /&gt;
: I found that I can better use Warp layer instead of Zoom to change size. But it'd be nice to have Amount duck for Zoom layer anyway...&lt;br /&gt;
:: The Amount parameter works exponentially; each time you add 1 to the Amount, the image is zoomed by a further factor of e (= 2.71828 or so).  Would a duck be any use if it just controlled the value of Amount in a linear way?&lt;br /&gt;
:: Workarounds include: export Amount, select it in the children dialog.  Whatever's selected in the children dialog shows a duck.  You can adjust it using that duck.&lt;br /&gt;
:: Also, if you use a Stretch layer, convert the Amount to Composite, export the X-Axis and connect it to the Y-Axis, then you have a duck-controllable fixed-aspect zoom. -- [[User:Dooglus|dooglus]] 15:32, 15 January 2008 (EST)&lt;br /&gt;
::: Yeah I found this workaround, but it's to much actions - i prefer better use Warp or Stretch layers. Why not the link Amount duck and Amount value with logarithmic function? ;) --[[User:Zelgadis|Zelgadis]] 10:33, 17 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatic colour palette optimisation ===&lt;br /&gt;
&lt;br /&gt;
(0) it would be nice to use libcontrast [http://david.navi.cx/blog/?p=132] [http://david.navi.cx/blog/?p=94] [http://david.navi.cx/blog/?p=99] [http://svn.gnome.org/svn/xchat-gnome/trunk/src/libcontrast/] to automatically adjust selected or all the palette items for best visual contrast. It would also be interesting to have a layer that uses this code to filter the image.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arbitrary Color Channels ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; The ability for the user to create any number of custom channels for various purposes.&lt;br /&gt;
&lt;br /&gt;
=== Autorecover History ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; It would be great if autorecover could also recover the associated history of a file in the event of a crash.&lt;br /&gt;
&lt;br /&gt;
=== Layer Convert ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;(4)&amp;lt;/strike&amp;gt; (2) &amp;amp;mdash; The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''&lt;br /&gt;
&lt;br /&gt;
=== Vector fill bucket ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[Region Layer|region layer]]). &amp;lt;p&amp;gt;Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;If this is implemented, it will probably be necessary to change the existing &amp;quot;fill&amp;quot; tool's name and icon to a &amp;quot;color injector&amp;quot; (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.&lt;br /&gt;
&lt;br /&gt;
*Inkscape has a very innvative version of this tool. Maybe you can just grab the code from there and integrate it in synfig? --[[User:SvH|SvH]] 01:37, 14 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== [[redraw tool]] ===&lt;br /&gt;
&lt;br /&gt;
(4-5) &amp;amp;mdash; Intutive reshaping of path-based layers. See link.&lt;br /&gt;
&lt;br /&gt;
=== [http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance] ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; This should solve all complaints about the layout, without requiring Synfig to be &amp;quot;just like program (x)&amp;quot;. See [[UI Reloaded]] for progress on this.&lt;br /&gt;
&lt;br /&gt;
=== Feedback for [[Smooth Move Tool]] ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; This tool does what a lot of folks are looking for, warping selected ducks in a &amp;quot;soft&amp;quot; fashion. But it's not very obvious what sort of effect it will have, from the tool's interface. It needs some sort of momentary center-of-action and radius indicator at the very least. Perhaps an &amp;quot;influence gradient&amp;quot; overlaid on the canvas once Synfig's core is sped up?&lt;br /&gt;
&lt;br /&gt;
=== Networkability ===&lt;br /&gt;
&lt;br /&gt;
(2) &amp;amp;mdash; Like Inkscape's &amp;quot;inkboard&amp;quot; feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option. This should probably farm off all the networking stuff to the telepathy framework so that synfig doesn't have to deal with all the account/etc issues.&lt;br /&gt;
&lt;br /&gt;
=== Intuitive tangent modification ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.&lt;br /&gt;
&lt;br /&gt;
-Agreed; blender does this with its IPO curves, and it's a really efficient way to work.&lt;br /&gt;
&lt;br /&gt;
=== Plugin API ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
=== Python support ===&lt;br /&gt;
&lt;br /&gt;
(1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.&lt;br /&gt;
&lt;br /&gt;
I suuose to join this request with [[Wish_list#a_realtime_.sif_synchronized_text_window]]. We can implement python access to XML DOM and write XML Editor in python. --[[User:AkhIL|AkhIL]] 06:54, 30 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== mod_synfig ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; For Apache. Render .sif to some format like png/mng on access.&lt;br /&gt;
&lt;br /&gt;
=== synfig nsplugin ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; Let Mozilla and Mozilla-based view synfig files in-browser.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Align function ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; Align objects at a common border (as in Inkscape)&lt;br /&gt;
&lt;br /&gt;
=== Improved SVG import ===&lt;br /&gt;
&lt;br /&gt;
(4) &amp;amp;mdash; Currently, all importing an SVG does is render it in ImageMagick. What I want is the ability to import the SVG document so that all the shapes, etc. of the SVG document show up as their equivilant synfig layers - i.e. if I had put them there myself. I'm trying to write a patch for this but the codebase is mostly undocumented. [[User:KMeist|KMeist]] 16:38, 25 Feb 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
[[svg2synfig]] could be incorporated using an open source XSLT processor. --[[User:Dmd|Dmd]] 13:34, 26 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Gradient Paint Tool ===&lt;br /&gt;
&lt;br /&gt;
How about a tool that can 'paint' a gradient object.  For example the options would be width and gradient type, one would make a stroke with the tool and the gradient would be automatically applied inside of the outline (set by width).  This would save the trouble of having to the all the encapsulation stuff. (Actually any tool that makes creating gradient one step would be good).--[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bone Animation Tools ===&lt;br /&gt;
&lt;br /&gt;
Bone system with inverse kinematics, very important for quick animation. You put bones on a drawed man and you can animate him like a puppet. I'm using that in Moho (lost marble product).--[[User:Ziolive|ziolive]] 23 Aug 2006&lt;br /&gt;
*I would find this very useful too. I think it is called '''rigging'''(4/5) --[[User:SvH|SvH]] 01:33, 14 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== AVI Backgrounds ===&lt;br /&gt;
Is there any way I can add an avi as a background so I could add facial expressions to a stop-motion animated figure. [zotz here, I was thinking DV background or extra timeline. I would like to mix animations with live footage. rating (3/4)]&lt;br /&gt;
&lt;br /&gt;
=== Character tool on Tool Options Dialog ===&lt;br /&gt;
&lt;br /&gt;
I want to use the as a character generator for a TV show. By using chroma key hide the background.  Even better interface to a video overlay card with Alpha blending.&lt;br /&gt;
&lt;br /&gt;
=== Collect for Publication ===&lt;br /&gt;
&lt;br /&gt;
(3/4) - (zotz) Menu item, functionality that would collect alll files referenced in a sif and place them all in a tgz for sending elsewhere or publishing anumations in source form.&lt;br /&gt;
&lt;br /&gt;
=== Object Library ===&lt;br /&gt;
&lt;br /&gt;
(3/4) - (zotz) Haven't thought this all through yet, but synfig could come with a library of categotrised &amp;quot;objects&amp;quot; with a copyleft license (GPL?  CC BY-SA?) An animation clip art type deal.&lt;br /&gt;
**I'd suggest this should be public domain and distributed by openclipart.org -- --[[User:PaulWise|pabs]]&lt;br /&gt;
&lt;br /&gt;
=== Flash Export ===&lt;br /&gt;
&lt;br /&gt;
(3/4) Well, might just be me but if there was a posiblity to  export in .swf or .fla, I think the project might become a lot more popular.[[User:Conceit|Conceit]]&lt;br /&gt;
&lt;br /&gt;
(4/5) I wholeheartedly agree. I would definitely use synfig more if this feature were added and it would most definitely increase popularity. [[User:cdj05a|cdj05a]]&lt;br /&gt;
&lt;br /&gt;
=== Single window ===&lt;br /&gt;
&lt;br /&gt;
Depending on individual desktop setups, single window is sometimes preferable to many  windows. Can we have a single-window option?&lt;br /&gt;
&lt;br /&gt;
Also, even with many windows, Windows-users especially might find it better if all the windows only appeared as a single one on the taskbar.&lt;br /&gt;
&lt;br /&gt;
=== Line width tool ===&lt;br /&gt;
(4) It will be good to have a tool for easy changing line width. There was a such tool in earlier versions, but it's not usable. I'm often use variable line width, when drawing in synfig, so it is important for me. -- [[User:Zelgadis|Zelgadis]] 2007-09-09&lt;br /&gt;
&lt;br /&gt;
: It is [[FAQ#Where did the polygon, draw, sketch, and width tools go?|still available]].  Also, you can turn on the width ducks, using Alt-5. -- [[User:Dooglus|dooglus]] 12:18, 9 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
:: It is available, but I never was able to figure out how it works. Alt-5 works, but it is hard to set width to zero, for example. -- [[User:Zelgadis|Zelgadis]] 2007-09-10&lt;br /&gt;
&lt;br /&gt;
::: Are you wanting something that works on one vertex at a time?  Or all the vertices in an area?  Apparently the width tool was designed to work on a bunch of vertices at once.  I didn't figure out how it works though, either. -- [[User:Dooglus|dooglus]] 16:57, 10 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
:::: Width tool is surely a mystery. :) I'm waiting for something that works on one vertex at time. I liked the way as width was changed in Moho (Anime Studio now) - there was a special width tool and holding left mouse button on the vertex and moving cursor left decreasing width value, moving right - increasing. Maybe it make sense to rework Width tool in such way. -- [[User:Zelgadis|Zelgadis]] 2007-09-13&lt;br /&gt;
&lt;br /&gt;
=== Export Wizard ===&lt;br /&gt;
&lt;br /&gt;
(2/4) Conversion and export to other file formats (mpg, avi, flash formats, others, and the synfig format) with a step by step wizard for choosing format and place of saving. Similar to Gimp's saving of .png files but for movie/video type files. --&lt;br /&gt;
[[User:Hiddenghost|hiddenghost]]&lt;br /&gt;
&lt;br /&gt;
=== Using Synfig as a portable app ===&lt;br /&gt;
&lt;br /&gt;
(3) This isn't really a feature request (though it could be) but I was wondering if synfig could be used as a portable application (as in www.portableapps.com). Does the windows install require registry access? i really want to use Synfig at work, but I'm reluctant to install it just in case it leave footprints in the regisitry or something, and it would be sweet to use it on my travels as well. Only thing is, I can't test it out at home because I am using Linux.&lt;br /&gt;
See also: http://portableapps.com/node/5761&lt;br /&gt;
[[User:Zenoscope|zenoscope]]&lt;br /&gt;
&lt;br /&gt;
This isn't currently possible without modifying the source code. That has been on my TODO list for ages [[User:PaulWise|pabs]] 01:17, 26 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Allow organize child valuenodes in an hierarchy ===&lt;br /&gt;
(3-2) And allow maintain the organization once the file is saved. At the moment they are reordered in alphabetical order which is useless and annoying.&lt;br /&gt;
&lt;br /&gt;
=== Triangle sliders to be always visible ===&lt;br /&gt;
(3) I would like that the triangle sliders from [[Colors Dialog]] and [[Gradient Editor Dialog]] were visible whatever color or channel you're editing. Some times when the color or channel is to bright or light the slider is difficult to distinguish. --[[User:Genete|Genete]] 14:30, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== XICC support ===&lt;br /&gt;
&lt;br /&gt;
It would be cool if synfigstudio had support for [http://burtonini.com/blog/computers/xicc XICC].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Area to Edit ===&lt;br /&gt;
&lt;br /&gt;
An option like blender - select area to update would be nice, so the only part of the image that updates when you add or change something is in the selected area&lt;br /&gt;
&lt;br /&gt;
ie. when working on a complex composition, studio doesn't know, when I tweak a tiny part of the composition, that only that part needs redrawing, so it redraws the whole thing.  It would be good if there was some way of telling it which part to focus on. -- [[User:Dooglus|dooglus]] 04:02, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Histograms ===&lt;br /&gt;
&lt;br /&gt;
 01:23  * AkhIL wish to have histograms and luma/color scope like [http://mac.softpedia.com/progScreenshots/Avid-Xpress-DV-Screenshot-14207.html] in synfig&lt;br /&gt;
&lt;br /&gt;
I've looked at those pictures but don't know what they're showing.  Can you describe what those scopes are doing, and what the histograms display?  ie. what are the X and Y axes of the histograms? -- [[User:Dooglus|dooglus]] 04:07, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
First look this description in blender wiki [http://wiki.blender.org/index.php/Manual/VSE_Modes]&lt;br /&gt;
&lt;br /&gt;
Ok There is four things.&lt;br /&gt;
* Upper left is Lumascope (Luma Waveform in blender). X-Axis represents image's X-Axys. Y-Axis  is average luminescence of column of pixels.&lt;br /&gt;
* Upper right is Chromascope (Chroma Vectorscope in blender). Just look description on blender wiki.&lt;br /&gt;
* Lower left is like Lumascope but for each channel &lt;br /&gt;
* Lower right is histograms. X is luminescence and Y is count of pixels with such luminiscence.&lt;br /&gt;
&lt;br /&gt;
=== Sound Layer ===&lt;br /&gt;
&lt;br /&gt;
(4) It would be a very good improvement if the sound system were implemented into synfig in [[Sound Layer | this]] way. --[[User:Genete|Genete]] 07:46, 8 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Rearrange the view of waypoints for Canvas param ===&lt;br /&gt;
As reported in [http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1888858&amp;amp;group_id=144022&amp;amp;atid=757416 Bug #1888858] waypoints are not displayed for canvas switch events.&lt;br /&gt;
I suggest to rearrange waypoints display according to [[Media:Canvas_prop.png|this scheme]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Width weigths ===&lt;br /&gt;
Is it possible to add &amp;quot;weigths&amp;quot; for widths? ^_^ I.e. width changes not all the way along the segment. Maybe something like a duck on bline which indicates the region where the width of current vertex isn't changed.&lt;br /&gt;
[[Media:width-proposal.png|Illustration here.]]&lt;br /&gt;
&lt;br /&gt;
More ideas around this concept in [http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-04-16.log this conversation]. Although the log of that day is very interesting the lines related to this idea are from 22:38 to 23:43. [[User:Genete|Genete]] 17:51, 16 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Improved Colour Dialog ===&lt;br /&gt;
How easy is it to stick in a colour square/wheel? Messing with sliders is somewhat obstructive.&lt;br /&gt;
&lt;br /&gt;
=== Insert Waypoints ===&lt;br /&gt;
A button to create a waypoint for every selected duck, in its current position. Moving each duck up a bit and down again quickly gets tedious.&lt;br /&gt;
:If the duck in question has already a waypoint then you don't need to move it to create a new waypoint. Just select the corresponding parameter in your child list panel and select 'Add Waypoint' from the right click context menu over the parameter. No need to have the duck selected. If you want to freeze the entire bline just do that over the Bline Point List. [[User:Genete|Genete]] 07:48, 29 April 2008 (EDT)&lt;br /&gt;
::Yes, but it would be nice to have opportunity to add waypoint to parameer which not have any ducks yet (i.e. non-animated parameter). --[[User:Zelgadis|Zelgadis]] 08:33, 29 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatically split tangeants ===&lt;br /&gt;
&lt;br /&gt;
Holding shift while moving tangeant ducks should automatically split them. They can be rejoined if necessary through the context menu as they are now.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Dev:Wish_list&amp;diff=7156</id>
		<title>Dev:Wish list</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Dev:Wish_list&amp;diff=7156"/>
				<updated>2008-05-14T05:33:33Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Bone Animation Tools */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''''Warning''''': We need more people working on the code if we are going to be able to achieve all the feature requests.&lt;br /&gt;
&lt;br /&gt;
Got a great idea for a new feature? Just add it here, or on the [http://sourceforge.net/tracker/?group_id=144022&amp;amp;atid=757419 feature requests tracker]. Before you do, please check the [http://svn.voria.com/code/ETL/trunk/TODO etl], [http://svn.voria.com/code/synfig-core/trunk/TODO synfig] and [http://svn.voria.com/code/synfig-studio/trunk/TODO synfigstudio] TODO files for similar ideas. Please add a rating of how essential this feature is to your workflow according to the following scale:&lt;br /&gt;
&lt;br /&gt;
#&amp;quot;Well, it might be nifty. To someone.&amp;quot;&lt;br /&gt;
#&amp;quot;I probably would make use this&amp;quot;&lt;br /&gt;
#&amp;quot;It's not essential, but I'd really like to have this at my disposal.&amp;quot;&lt;br /&gt;
#&amp;quot;Synfig would be soooo much better with this change&amp;quot;&lt;br /&gt;
#&amp;quot;I can't/won't use Synfig without it!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== Wishes ==&lt;br /&gt;
&lt;br /&gt;
=== get_color method in text and radial blur ===&lt;br /&gt;
&lt;br /&gt;
[5] Without get_color method distorion produces artifacts &lt;br /&gt;
[http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1831355&amp;amp;group_id=144022&amp;amp;atid=757416 bug  1831355]. So I would like to get this problem fixed before doing something else. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== Full functional of group dialog ===&lt;br /&gt;
&lt;br /&gt;
[5] Group dialog is broken now [http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1796833&amp;amp;group_id=144022&amp;amp;atid=757416 bug 1796833]. So we should get old features work right before making new one. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== import/export .swf files ===&lt;br /&gt;
&lt;br /&gt;
very important productivity feature&lt;br /&gt;
&lt;br /&gt;
=== import/export .svg frames sequence, and/or .svg animations ===&lt;br /&gt;
&lt;br /&gt;
very important productivity feature&lt;br /&gt;
&lt;br /&gt;
=== a realtime .sif synchronized text window ===&lt;br /&gt;
&lt;br /&gt;
just like the xml editor of Inkscape, or the html editor in Dreamweaver (this is hugelly useful for productivity)&lt;br /&gt;
&lt;br /&gt;
I thinks scripting API can be implement in this way. For example you make XML DOM like implementation for python which alows to change DOM tree from python code and see chenges in canvas. By this way you can implement import/export scripts. Automation scripts. And a lot of different things. Even synchronization of animation between blender and synfig. --[[User:AkhIL|AkhIL]] 23:10, 26 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== choosing colour from gimp/inkscape palettes ===&lt;br /&gt;
&lt;br /&gt;
very useful when you need some colour comformity of what you're doing &lt;br /&gt;
&lt;br /&gt;
=== Good high-level documentation of the source code ===&lt;br /&gt;
&lt;br /&gt;
(2) It'd be nice if a newbie could quickly navigate around the source code. The best thing to do would be to add top-level comments in each file, explaining what that file does, a README.TXT in each directory, explaining what's in that directory. This would be pretty fast and easy to do, and make it much easier for new programmers to join. &lt;br /&gt;
&lt;br /&gt;
Time permitting, it would also be good to document on a high level what the data structures are, but that's harder, since those tend to evolve, and it is often difficult to keep in sync. It would also be useful to document what individual functions do (just a one-liner high-level description), but that also takes more time.&lt;br /&gt;
: There is a page link in the wiki that connect to the [http://www.synfig.com/doc Synfig API Documentation]. I think this link should be highlighted to be more accessible for newbies contributors and mature developers (the link was found [[Releases/DeveloperPreview#Support | here]]). --[[User:Genete|Genete]] 10:02, 11 December 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Mathematical functions to animate ===&lt;br /&gt;
(2/4) If you want to make a waving flag, it would be handful a sine function, tuned with random correctors, for example. &lt;br /&gt;
: -This should generate waypoints each 1, 2, 4 frames or any other step at artist's wish.&lt;br /&gt;
: -When applying a function you can add it to current values, add it to 1st frame values or simply override old values. Perhaps other options (such multiplication) would be fine, too. Something like texture editor in [http://www.artofillusion.org Art of Illusion], perhaps.&lt;br /&gt;
Perhaps it would be useful reusing the [http://www.gnu.org/software/octave/ Octave] source code to parse mathematical expressions.&lt;br /&gt;
I have rated this wish with a '2' because undoubtly many users will not be familiar to mathematical concepts, but for those who will be, I'd rate it with a 4. It would be possible to make a ball describing a parabolic moving in no time.&lt;br /&gt;
[[User:ajotatxe|ajotatxe]] 20 November 2007&lt;br /&gt;
: dooglus can probably chime in better than I here (see his example of balls on mathematical paths at http://uk.youtube.com/watch?v=YTpSfUthuVE ), but I believe that this is already possible.  Synfig does support a variety of mathematical transforms for parameters, although the way you do this is by no means intuitive.  (You might also want to check out the preambletaffy.sifz example for an easier approach to a waving flag. I know you were just using that as an example, but for the record...) [[User:Pxegeek|Pxegeek]] 00:58, 21 November 2007 (EST)&lt;br /&gt;
&lt;br /&gt;
: I'd also rate it with a (4) (and updated the rating accordingly), not for this special case, but to make many workarounds much easier.  Simulating [Parabolic Shot|free fall], for example, would be a lot easier with real formulas.  I don't know, though how easy it will be to implement, maybe waiting for a scripting interface to be implemented is better than hacking this feature in an ad-hoc manner.  --[[User:Rubikcube|Rubikcube]] 16:38, 29 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Warning about editing bizarre things in animate editing mode ===&lt;br /&gt;
(3.5) It seems to have little sense animate certain things like Blend Method or Type of Feather. It would be very nice that the program asked comfirmation if you change these attributes in animate editing mode. If you do want to, you would have three options: &amp;quot;Yes, never ask&amp;quot;, &amp;quot;Yes, never ask for this attribute&amp;quot;, &amp;quot;No&amp;quot;. I guess that internally, this attributes has integer type (or something like that) and the attributes that you normally want to animate, float type, so I think that this feature is relatively easy to implement. My English is not very good, so please feel free to fix this post.&lt;br /&gt;
[[User:ajotatxe|ajotatxe]] 20 November 2007&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bones with FK &amp;amp; IK + grouping of objects into folders ===&lt;br /&gt;
&lt;br /&gt;
(1) Bones cane move specific vector assigned to them or the bones can have envelopes that move the vectors within their field of influence, much Like Anime Studio/Moho does. It's quite a time saving process of animating. Objects created can be saved into separate groups or folders using the same system as Anime Studio/Moho -Shadowphoenix 27/8/2007&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Animated sketch ===&lt;br /&gt;
&lt;br /&gt;
(1) it would be great, if the tool Sketch was animatable (for example, in a form of a special sketch-layer). --Zelgadis 2007-06-14&lt;br /&gt;
&lt;br /&gt;
=== Duck for Amount value in Zoom layer ===&lt;br /&gt;
&lt;br /&gt;
(2) It would be nice if Amount value in Zoom layer was controlled by additional duck. --[[User:Zelgadis|Zelgadis]] 02:49, 29 December 2007 (EST)&lt;br /&gt;
: I found that I can better use Warp layer instead of Zoom to change size. But it'd be nice to have Amount duck for Zoom layer anyway...&lt;br /&gt;
:: The Amount parameter works exponentially; each time you add 1 to the Amount, the image is zoomed by a further factor of e (= 2.71828 or so).  Would a duck be any use if it just controlled the value of Amount in a linear way?&lt;br /&gt;
:: Workarounds include: export Amount, select it in the children dialog.  Whatever's selected in the children dialog shows a duck.  You can adjust it using that duck.&lt;br /&gt;
:: Also, if you use a Stretch layer, convert the Amount to Composite, export the X-Axis and connect it to the Y-Axis, then you have a duck-controllable fixed-aspect zoom. -- [[User:Dooglus|dooglus]] 15:32, 15 January 2008 (EST)&lt;br /&gt;
::: Yeah I found this workaround, but it's to much actions - i prefer better use Warp or Stretch layers. Why not the link Amount duck and Amount value with logarithmic function? ;) --[[User:Zelgadis|Zelgadis]] 10:33, 17 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatic colour palette optimisation ===&lt;br /&gt;
&lt;br /&gt;
(0) it would be nice to use libcontrast [http://david.navi.cx/blog/?p=132] [http://david.navi.cx/blog/?p=94] [http://david.navi.cx/blog/?p=99] [http://svn.gnome.org/svn/xchat-gnome/trunk/src/libcontrast/] to automatically adjust selected or all the palette items for best visual contrast. It would also be interesting to have a layer that uses this code to filter the image.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arbitrary Color Channels ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; The ability for the user to create any number of custom channels for various purposes.&lt;br /&gt;
&lt;br /&gt;
=== Autorecover History ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; It would be great if autorecover could also recover the associated history of a file in the event of a crash.&lt;br /&gt;
&lt;br /&gt;
=== Layer Convert ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;(4)&amp;lt;/strike&amp;gt; (2) &amp;amp;mdash; The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''&lt;br /&gt;
&lt;br /&gt;
=== Vector fill bucket ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[Region Layer|region layer]]). &amp;lt;p&amp;gt;Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)&amp;lt;/p&amp;gt;&amp;lt;p&amp;gt;If this is implemented, it will probably be necessary to change the existing &amp;quot;fill&amp;quot; tool's name and icon to a &amp;quot;color injector&amp;quot; (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.&lt;br /&gt;
&lt;br /&gt;
=== [[redraw tool]] ===&lt;br /&gt;
&lt;br /&gt;
(4-5) &amp;amp;mdash; Intutive reshaping of path-based layers. See link.&lt;br /&gt;
&lt;br /&gt;
=== [http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance] ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;mdash; This should solve all complaints about the layout, without requiring Synfig to be &amp;quot;just like program (x)&amp;quot;. See [[UI Reloaded]] for progress on this.&lt;br /&gt;
&lt;br /&gt;
=== Feedback for [[Smooth Move Tool]] ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; This tool does what a lot of folks are looking for, warping selected ducks in a &amp;quot;soft&amp;quot; fashion. But it's not very obvious what sort of effect it will have, from the tool's interface. It needs some sort of momentary center-of-action and radius indicator at the very least. Perhaps an &amp;quot;influence gradient&amp;quot; overlaid on the canvas once Synfig's core is sped up?&lt;br /&gt;
&lt;br /&gt;
=== Networkability ===&lt;br /&gt;
&lt;br /&gt;
(2) &amp;amp;mdash; Like Inkscape's &amp;quot;inkboard&amp;quot; feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option. This should probably farm off all the networking stuff to the telepathy framework so that synfig doesn't have to deal with all the account/etc issues.&lt;br /&gt;
&lt;br /&gt;
=== Intuitive tangent modification ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.&lt;br /&gt;
&lt;br /&gt;
-Agreed; blender does this with its IPO curves, and it's a really efficient way to work.&lt;br /&gt;
&lt;br /&gt;
=== Plugin API ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
=== Python support ===&lt;br /&gt;
&lt;br /&gt;
(1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.&lt;br /&gt;
&lt;br /&gt;
I suuose to join this request with [[Wish_list#a_realtime_.sif_synchronized_text_window]]. We can implement python access to XML DOM and write XML Editor in python. --[[User:AkhIL|AkhIL]] 06:54, 30 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== mod_synfig ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; For Apache. Render .sif to some format like png/mng on access.&lt;br /&gt;
&lt;br /&gt;
=== synfig nsplugin ===&lt;br /&gt;
&lt;br /&gt;
(1) &amp;amp;mdash; Let Mozilla and Mozilla-based view synfig files in-browser.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Align function ===&lt;br /&gt;
&lt;br /&gt;
(3) &amp;amp;mdash; Align objects at a common border (as in Inkscape)&lt;br /&gt;
&lt;br /&gt;
=== Improved SVG import ===&lt;br /&gt;
&lt;br /&gt;
(4) &amp;amp;mdash; Currently, all importing an SVG does is render it in ImageMagick. What I want is the ability to import the SVG document so that all the shapes, etc. of the SVG document show up as their equivilant synfig layers - i.e. if I had put them there myself. I'm trying to write a patch for this but the codebase is mostly undocumented. [[User:KMeist|KMeist]] 16:38, 25 Feb 2006 (PST)&lt;br /&gt;
&lt;br /&gt;
[[svg2synfig]] could be incorporated using an open source XSLT processor. --[[User:Dmd|Dmd]] 13:34, 26 January 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Gradient Paint Tool ===&lt;br /&gt;
&lt;br /&gt;
How about a tool that can 'paint' a gradient object.  For example the options would be width and gradient type, one would make a stroke with the tool and the gradient would be automatically applied inside of the outline (set by width).  This would save the trouble of having to the all the encapsulation stuff. (Actually any tool that makes creating gradient one step would be good).--[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Bone Animation Tools ===&lt;br /&gt;
&lt;br /&gt;
Bone system with inverse kinematics, very important for quick animation. You put bones on a drawed man and you can animate him like a puppet. I'm using that in Moho (lost marble product).--[[User:Ziolive|ziolive]] 23 Aug 2006&lt;br /&gt;
*I would find this very useful too. I think it is called '''rigging'''(4/5) --[[User:SvH|SvH]] 01:33, 14 May 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== AVI Backgrounds ===&lt;br /&gt;
Is there any way I can add an avi as a background so I could add facial expressions to a stop-motion animated figure. [zotz here, I was thinking DV background or extra timeline. I would like to mix animations with live footage. rating (3/4)]&lt;br /&gt;
&lt;br /&gt;
=== Character tool on Tool Options Dialog ===&lt;br /&gt;
&lt;br /&gt;
I want to use the as a character generator for a TV show. By using chroma key hide the background.  Even better interface to a video overlay card with Alpha blending.&lt;br /&gt;
&lt;br /&gt;
=== Collect for Publication ===&lt;br /&gt;
&lt;br /&gt;
(3/4) - (zotz) Menu item, functionality that would collect alll files referenced in a sif and place them all in a tgz for sending elsewhere or publishing anumations in source form.&lt;br /&gt;
&lt;br /&gt;
=== Object Library ===&lt;br /&gt;
&lt;br /&gt;
(3/4) - (zotz) Haven't thought this all through yet, but synfig could come with a library of categotrised &amp;quot;objects&amp;quot; with a copyleft license (GPL?  CC BY-SA?) An animation clip art type deal.&lt;br /&gt;
**I'd suggest this should be public domain and distributed by openclipart.org -- --[[User:PaulWise|pabs]]&lt;br /&gt;
&lt;br /&gt;
=== Flash Export ===&lt;br /&gt;
&lt;br /&gt;
(3/4) Well, might just be me but if there was a posiblity to  export in .swf or .fla, I think the project might become a lot more popular.[[User:Conceit|Conceit]]&lt;br /&gt;
&lt;br /&gt;
(4/5) I wholeheartedly agree. I would definitely use synfig more if this feature were added and it would most definitely increase popularity. [[User:cdj05a|cdj05a]]&lt;br /&gt;
&lt;br /&gt;
=== Single window ===&lt;br /&gt;
&lt;br /&gt;
Depending on individual desktop setups, single window is sometimes preferable to many  windows. Can we have a single-window option?&lt;br /&gt;
&lt;br /&gt;
Also, even with many windows, Windows-users especially might find it better if all the windows only appeared as a single one on the taskbar.&lt;br /&gt;
&lt;br /&gt;
=== Line width tool ===&lt;br /&gt;
(4) It will be good to have a tool for easy changing line width. There was a such tool in earlier versions, but it's not usable. I'm often use variable line width, when drawing in synfig, so it is important for me. -- [[User:Zelgadis|Zelgadis]] 2007-09-09&lt;br /&gt;
&lt;br /&gt;
: It is [[FAQ#Where did the polygon, draw, sketch, and width tools go?|still available]].  Also, you can turn on the width ducks, using Alt-5. -- [[User:Dooglus|dooglus]] 12:18, 9 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
:: It is available, but I never was able to figure out how it works. Alt-5 works, but it is hard to set width to zero, for example. -- [[User:Zelgadis|Zelgadis]] 2007-09-10&lt;br /&gt;
&lt;br /&gt;
::: Are you wanting something that works on one vertex at a time?  Or all the vertices in an area?  Apparently the width tool was designed to work on a bunch of vertices at once.  I didn't figure out how it works though, either. -- [[User:Dooglus|dooglus]] 16:57, 10 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
:::: Width tool is surely a mystery. :) I'm waiting for something that works on one vertex at time. I liked the way as width was changed in Moho (Anime Studio now) - there was a special width tool and holding left mouse button on the vertex and moving cursor left decreasing width value, moving right - increasing. Maybe it make sense to rework Width tool in such way. -- [[User:Zelgadis|Zelgadis]] 2007-09-13&lt;br /&gt;
&lt;br /&gt;
=== Export Wizard ===&lt;br /&gt;
&lt;br /&gt;
(2/4) Conversion and export to other file formats (mpg, avi, flash formats, others, and the synfig format) with a step by step wizard for choosing format and place of saving. Similar to Gimp's saving of .png files but for movie/video type files. --&lt;br /&gt;
[[User:Hiddenghost|hiddenghost]]&lt;br /&gt;
&lt;br /&gt;
=== Using Synfig as a portable app ===&lt;br /&gt;
&lt;br /&gt;
(3) This isn't really a feature request (though it could be) but I was wondering if synfig could be used as a portable application (as in www.portableapps.com). Does the windows install require registry access? i really want to use Synfig at work, but I'm reluctant to install it just in case it leave footprints in the regisitry or something, and it would be sweet to use it on my travels as well. Only thing is, I can't test it out at home because I am using Linux.&lt;br /&gt;
See also: http://portableapps.com/node/5761&lt;br /&gt;
[[User:Zenoscope|zenoscope]]&lt;br /&gt;
&lt;br /&gt;
This isn't currently possible without modifying the source code. That has been on my TODO list for ages [[User:PaulWise|pabs]] 01:17, 26 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Allow organize child valuenodes in an hierarchy ===&lt;br /&gt;
(3-2) And allow maintain the organization once the file is saved. At the moment they are reordered in alphabetical order which is useless and annoying.&lt;br /&gt;
&lt;br /&gt;
=== Triangle sliders to be always visible ===&lt;br /&gt;
(3) I would like that the triangle sliders from [[Colors Dialog]] and [[Gradient Editor Dialog]] were visible whatever color or channel you're editing. Some times when the color or channel is to bright or light the slider is difficult to distinguish. --[[User:Genete|Genete]] 14:30, 29 October 2007 (EDT)&lt;br /&gt;
&lt;br /&gt;
=== XICC support ===&lt;br /&gt;
&lt;br /&gt;
It would be cool if synfigstudio had support for [http://burtonini.com/blog/computers/xicc XICC].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Area to Edit ===&lt;br /&gt;
&lt;br /&gt;
An option like blender - select area to update would be nice, so the only part of the image that updates when you add or change something is in the selected area&lt;br /&gt;
&lt;br /&gt;
ie. when working on a complex composition, studio doesn't know, when I tweak a tiny part of the composition, that only that part needs redrawing, so it redraws the whole thing.  It would be good if there was some way of telling it which part to focus on. -- [[User:Dooglus|dooglus]] 04:02, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Histograms ===&lt;br /&gt;
&lt;br /&gt;
 01:23  * AkhIL wish to have histograms and luma/color scope like [http://mac.softpedia.com/progScreenshots/Avid-Xpress-DV-Screenshot-14207.html] in synfig&lt;br /&gt;
&lt;br /&gt;
I've looked at those pictures but don't know what they're showing.  Can you describe what those scopes are doing, and what the histograms display?  ie. what are the X and Y axes of the histograms? -- [[User:Dooglus|dooglus]] 04:07, 3 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
First look this description in blender wiki [http://wiki.blender.org/index.php/Manual/VSE_Modes]&lt;br /&gt;
&lt;br /&gt;
Ok There is four things.&lt;br /&gt;
* Upper left is Lumascope (Luma Waveform in blender). X-Axis represents image's X-Axys. Y-Axis  is average luminescence of column of pixels.&lt;br /&gt;
* Upper right is Chromascope (Chroma Vectorscope in blender). Just look description on blender wiki.&lt;br /&gt;
* Lower left is like Lumascope but for each channel &lt;br /&gt;
* Lower right is histograms. X is luminescence and Y is count of pixels with such luminiscence.&lt;br /&gt;
&lt;br /&gt;
=== Sound Layer ===&lt;br /&gt;
&lt;br /&gt;
(4) It would be a very good improvement if the sound system were implemented into synfig in [[Sound Layer | this]] way. --[[User:Genete|Genete]] 07:46, 8 February 2008 (EST)&lt;br /&gt;
&lt;br /&gt;
=== Rearrange the view of waypoints for Canvas param ===&lt;br /&gt;
As reported in [http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1888858&amp;amp;group_id=144022&amp;amp;atid=757416 Bug #1888858] waypoints are not displayed for canvas switch events.&lt;br /&gt;
I suggest to rearrange waypoints display according to [[Media:Canvas_prop.png|this scheme]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Width weigths ===&lt;br /&gt;
Is it possible to add &amp;quot;weigths&amp;quot; for widths? ^_^ I.e. width changes not all the way along the segment. Maybe something like a duck on bline which indicates the region where the width of current vertex isn't changed.&lt;br /&gt;
[[Media:width-proposal.png|Illustration here.]]&lt;br /&gt;
&lt;br /&gt;
More ideas around this concept in [http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-04-16.log this conversation]. Although the log of that day is very interesting the lines related to this idea are from 22:38 to 23:43. [[User:Genete|Genete]] 17:51, 16 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Improved Colour Dialog ===&lt;br /&gt;
How easy is it to stick in a colour square/wheel? Messing with sliders is somewhat obstructive.&lt;br /&gt;
&lt;br /&gt;
=== Insert Waypoints ===&lt;br /&gt;
A button to create a waypoint for every selected duck, in its current position. Moving each duck up a bit and down again quickly gets tedious.&lt;br /&gt;
:If the duck in question has already a waypoint then you don't need to move it to create a new waypoint. Just select the corresponding parameter in your child list panel and select 'Add Waypoint' from the right click context menu over the parameter. No need to have the duck selected. If you want to freeze the entire bline just do that over the Bline Point List. [[User:Genete|Genete]] 07:48, 29 April 2008 (EDT)&lt;br /&gt;
::Yes, but it would be nice to have opportunity to add waypoint to parameer which not have any ducks yet (i.e. non-animated parameter). --[[User:Zelgadis|Zelgadis]] 08:33, 29 April 2008 (EDT)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Automatically split tangeants ===&lt;br /&gt;
&lt;br /&gt;
Holding shift while moving tangeant ducks should automatically split them. They can be rejoined if necessary through the context menu as they are now.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Doc:Brushes&amp;diff=7113</id>
		<title>Doc:Brushes</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Doc:Brushes&amp;diff=7113"/>
				<updated>2008-05-10T10:02:47Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* A brush image */ Added some of my brush pictures&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
The Outlines that you can draw with Synfig are formed by a rounded brush. The brush is defined by a radius that you can modify by its brush editor widget. This tutorial explains how to make brushed outlines that would improve sustantially your artwork.&lt;br /&gt;
&lt;br /&gt;
== What do I need to use brushes? ==&lt;br /&gt;
&lt;br /&gt;
=== A brush image ===&lt;br /&gt;
Well, for the moment Synfig hasn't any brush image included so you'll need to do them by your self or grab from the free resources (insert link here to those resources). &lt;br /&gt;
&lt;br /&gt;
Here are some examples of brushes:&lt;br /&gt;
&lt;br /&gt;
[[Image:Soft-wheezy-asymetric-brush.png]]&lt;br /&gt;
[[Image:Wool-ball-brush.png]]&lt;br /&gt;
[[Image:Soft-triangle-brush.png]]&lt;br /&gt;
[[Image:Tictactoe-brush.png]]&lt;br /&gt;
[[Image:Rhomb-fuzzy-brush.png]]&lt;br /&gt;
[[Image:Big-soft-brush.png|left]]&lt;br /&gt;
These pictures are all licensed as public domain. Feel free to use them in your projects.&lt;br /&gt;
&lt;br /&gt;
Brush images can just be any kind of image file that allows transparency (PNG, TIFF, GIF). The more resolution your image has, the bigger your brush size can be without pixelisation. Huge file sizes would take synfig more time to render,though. Find the balance between both options of quality and speed.&lt;br /&gt;
&lt;br /&gt;
Anyway, you can use anything that is visible under synfig as a brush. See below.&lt;br /&gt;
&lt;br /&gt;
=== A recent Release ===&lt;br /&gt;
&lt;br /&gt;
Brushes are not a primary feature of Synfig. They are obtained from the combintation of the following features:&lt;br /&gt;
&lt;br /&gt;
* [[Duplicate Layer]] what implies SVN revision &amp;gt;= 1358&lt;br /&gt;
* Link to Bline (what uses the following convert types):&lt;br /&gt;
** [[Convert#Bline Vertex|Bline Vertex]], what implies SVN revision &amp;gt;= 774&lt;br /&gt;
** [[Convert#Bline Tangent|Bline Tangent]], what implies SVN revision &amp;gt;= 1863&lt;br /&gt;
** [[Convert#Bline Width|Bline Width]], what implies SVN revision &amp;gt;= 1872&lt;br /&gt;
&lt;br /&gt;
Strictly the Link to Bline feature is not needed but it would help on make several conversion types and linking.&lt;br /&gt;
&lt;br /&gt;
== The Idea ==&lt;br /&gt;
&lt;br /&gt;
The idea of brushes is to use the Duplicate layer feature with the Link to Bline (automatic or manual) feature given by the conversion types.&lt;br /&gt;
&lt;br /&gt;
When you link a vertex to a bline (or a tangent or a width) it converts your parameter to the following sub-parameters.&lt;br /&gt;
&lt;br /&gt;
* bline &amp;quot;BLine&amp;quot; &lt;br /&gt;
* bool &amp;quot;Loop&amp;quot; &lt;br /&gt;
* real &amp;quot;Amount&amp;quot;&lt;br /&gt;
&lt;br /&gt;
There are other particular paramters for tangent or width that will be revised in other section.&lt;br /&gt;
&lt;br /&gt;
bline &amp;quot;Bline&amp;quot; is the bline where the parameter (vertex, tangent or width) is linked to. In the case of the vertex it means that the vertex lies on the bline given by its &amp;quot;Amount&amp;quot; parameter. When Amount is 0.0 the vertex position is the Bline begin. When Amount is 1.0 the vertex position is the Bline end. When Loop is &amp;quot;on&amp;quot; values outside the [0.0, 1.0] range are forced to be in that range by eliminating the integer part of the number. &amp;lt;small&amp;gt;&amp;lt;tt&amp;gt;(It needs a better explanation)&amp;lt;/tt&amp;gt;&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
On the other hand the Duplicate layer allows duplicate the render of everything that is below it as many times as the Index parameter indicates. Also if you link any parameter to that Index one the parameter is modified according to the index before it is multiple rendered by the Duplicate layer. It allows apply some kind of transformation to the layers at the same time you duplicate them. &lt;br /&gt;
&lt;br /&gt;
Combining those two features (Link to Bline and Duplicate) you can achieve the emulation of brushes in synfig.&lt;br /&gt;
&lt;br /&gt;
== The procedure ==&lt;br /&gt;
It is supposed you already have an outline wher you would like to apply the brush. If not available create it now. &lt;br /&gt;
&lt;br /&gt;
These are the steps you need to follow:&lt;br /&gt;
&lt;br /&gt;
# Caret Menu-&amp;gt;File-&amp;gt;Import. Select your image file for the brush. You can also use an existing layer to do that, even a canvas with an animation inside. It doesn't matter what you use as brush, the procedure is always the same.&lt;br /&gt;
# Create a Rotate layer onto the brush layer.&lt;br /&gt;
# Create a Zoom layer onto the Rotate layer.&lt;br /&gt;
# Select Zoom, Rotate and your brush layer and encapsulate them. It would produce a Paste Canvas Layer. &lt;br /&gt;
# Select the Paste Canvas Layer and also select your outline layer. Make click on the Paste Canvas Layer Origin duck (beware that it can be below the Origin of the outline layer -both at (0,0) by default-) and make right click on the outline (avoid any duck). Select the &amp;quot;Link to Bline&amp;quot; option.&lt;br /&gt;
# Repeat above step but do it with the angle duck of the Rotate layer instead of the Origin of the Paste Canvas Layer. It doesn't matter if you make right click on the same place of the outline bline or not. Later it will be fixed.&lt;br /&gt;
# Repeat the same but with the Amount paramter of the Zoom layer. AS well as the Amount parameter of the zoom layer has not visual interface (hasn't any duck associated) you have to export the parameter (right click export) and then select it from the Child panel. Then you can make the right click and Link to Bline operations.&lt;br /&gt;
# Onto the Paste Canvas layer create a Duplicate Layer. Encalsulate both to avoid unuseful duplications of the stuff below the Duplciate Layer. It would produce a Child parameter (probably called &amp;quot;Index1&amp;quot; if that's your first Duplicate layer). Select the Index parameter from the Child Panel. &lt;br /&gt;
# Now go to the Paste canvas layer. Search for the Origin parameter (that now is a converted type) and expand it. Look for the Amount parameter. This parameter should have a value between 0.0 and 1.0 depending on where did you made click to the outline. Make right click over it and select Convert-&amp;gt;Scale. Expand it again and select the &amp;quot;Link&amp;quot; parameter (it should be a Real) and make right click and select &amp;quot;Connect&amp;quot;. It would connect the Link parameter to the Index parameter (already selected from the child panel). The default values for Index parameter is to duplicate from 1.0 to 3.0 so a this moment the duplicated brushes images are all placed at the end of the outline bline because all they have a value bigger or equal than 1.0. &lt;br /&gt;
#Repeat the same procedure for the Amount sub-parameter of the Angle parameter of the Rotate layer and the Amount sub-parameter of the Amount parameter of the Zoom layer.&lt;br /&gt;
# It is the time of spread the position of the duplicated brushes along the bline. To do that you have to properly scale the Amount sub-parameter of each converted to Link to Bline parameter. Go to the Paste Canvas Layer and expand the Origin parameter. Expand the Amount sub-parameter (already converted to a Scale) and look to the &amp;quot;Scale&amp;quot; parameter. This paramter has a default value of 1.0. Make right click over it and select Covnert-&amp;gt;Reciprocal. It would produce two sub-parameter more: Link, Epsilon and Infinite. Leave Epsilon and Infinite as they are and modify the Link one to be 3.0. Voila! the brush is spreaded along the bline!&lt;br /&gt;
# Now export the Link sub-parameter (that you have just modified) by right click and &amp;quot;Export&amp;quot;. Give a meaning name (for example &amp;quot;b-amount&amp;quot;)&lt;br /&gt;
# Go to the child panel and select the just exported one. &lt;br /&gt;
# Without leaving the Origin parameter search for the following sub-parameter: Origin(Bline Origin)-&amp;gt;Amount(Scale)-&amp;gt;Link(Duplicate)-&amp;gt;To. This parameter is the end of the loop of the Duplciate layer. Select it and make right click. As well as the exported b-amount is selected you can select Link from the context menu. It would make the Duplicate layer repeat it as many times says the b-amount value. By going to the Child Panel and changing the &amp;quot;b-amount&amp;quot; parameter to a high value (for example 100) make the brush to fill all the bline. Do you get the idea?&lt;br /&gt;
# Repeat the same procedure to the following parameters of the following layers (keep in mind that the &amp;quot;b-amount&amp;quot; parameter from the child list panel still selected):&lt;br /&gt;
## Rotate Layer-&amp;gt;Amount(Bline Angle)-&amp;gt;Amount(Scale)-&amp;gt;Link(Duplicate)-&amp;gt;To. Select it and right click &amp;quot;Link&amp;quot;.&lt;br /&gt;
## Zoom Layer-&amp;gt;Amount(Bline Width)-&amp;gt;Amount(Scale)-&amp;gt;Link(Duplicate)-&amp;gt;To. Select it and right click &amp;quot;Link&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You can make the outline layer invisible (by unchecking the visibility check box) to only render the brushed one.&lt;br /&gt;
&lt;br /&gt;
It only rest to make some modifications to the Outline width and the ouline shape to modify the brushed one accordingly.&lt;br /&gt;
&lt;br /&gt;
Also you would like to not link the rotation to the bline to achieve a constant angled pen. It is up to you to use one or other feature.&lt;br /&gt;
&lt;br /&gt;
There is a problem with the Zoom option. The zoom is an exponential value and the width is a linear one. It means that Zoom = 0 is current size, negative values means zoom out and positive values means zoom in. To link properly the width to the zoom we need a logarithmic convert type that is not available at the moment. So to solve that you have to make the Zoom parameter of the Paste canvas layer to be a negative value (between -3 and -5 are good values for normal brush sizes) and then let the Zoom Layer do its work. There is not fixed rule for this interim  solution.&lt;br /&gt;
&lt;br /&gt;
== Further steps ==&lt;br /&gt;
&lt;br /&gt;
It is possible to make more funcy things with this procedure like make random angled brushes or random spreaded brushes stamps along the outline. But this is part of an Advanced uses of Brushes tutorial.&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
[[Image:Test1-1.png]]&lt;br /&gt;
&lt;br /&gt;
A Star layer.&lt;br /&gt;
You can see that seems to be a bug there with the feather and zoom in and out combinations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Test1-2.png]]&lt;br /&gt;
&lt;br /&gt;
A simple stroke.&lt;br /&gt;
&lt;br /&gt;
[[Image:Test1-3.png]]&lt;br /&gt;
&lt;br /&gt;
A angled pen.&lt;br /&gt;
And this is the brush image: &lt;br /&gt;
&lt;br /&gt;
[[Image:Brush002.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Test1-4.png]]&lt;br /&gt;
&lt;br /&gt;
The same but not rotated.&lt;br /&gt;
&lt;br /&gt;
[[Image:Test1-5.png]]&lt;br /&gt;
&lt;br /&gt;
Other brush example. And this is the brush image:&lt;br /&gt;
&lt;br /&gt;
[[Image:Brush001.png|128px]]&lt;br /&gt;
&lt;br /&gt;
This is the sifz file used to render the examples:&lt;br /&gt;
&lt;br /&gt;
[[Media:Test1.sifz|Sample file link]]&lt;br /&gt;
&lt;br /&gt;
You need to modify the zoom parameter in the Paste canvas layer and the b-amount valuenode to modify the density of the brush to achieve same values than in the examples.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=File:Soft-wheezy-asymetric-brush.png&amp;diff=7112</id>
		<title>File:Soft-wheezy-asymetric-brush.png</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=File:Soft-wheezy-asymetric-brush.png&amp;diff=7112"/>
				<updated>2008-05-10T09:48:22Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: A sample brush file, which i release into public domain for all to use freely and without restrictions.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A sample brush file, which i release into public domain for all to use freely and without restrictions.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=File:Soft-triangle-brush.png&amp;diff=7111</id>
		<title>File:Soft-triangle-brush.png</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=File:Soft-triangle-brush.png&amp;diff=7111"/>
				<updated>2008-05-10T09:47:44Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: A sample brush file, which i release into public domain for all to use freely and without restrictions.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A sample brush file, which i release into public domain for all to use freely and without restrictions.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=File:Tictactoe-brush.png&amp;diff=7110</id>
		<title>File:Tictactoe-brush.png</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=File:Tictactoe-brush.png&amp;diff=7110"/>
				<updated>2008-05-10T09:47:00Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: A sample brush file, which i release into public domain for all to use freely and without restrictions.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A sample brush file, which i release into public domain for all to use freely and without restrictions.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=File:Wool-ball-brush.png&amp;diff=7109</id>
		<title>File:Wool-ball-brush.png</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=File:Wool-ball-brush.png&amp;diff=7109"/>
				<updated>2008-05-10T09:46:22Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: A sample brush file, which i release into public domain for all to use freely and without restrictions.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A sample brush file, which i release into public domain for all to use freely and without restrictions.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=File:Rhomb-fuzzy-brush.png&amp;diff=7108</id>
		<title>File:Rhomb-fuzzy-brush.png</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=File:Rhomb-fuzzy-brush.png&amp;diff=7108"/>
				<updated>2008-05-10T09:45:22Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: A sample brush file, which i release into public domain for all to use freely and without restrictions.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A sample brush file, which i release into public domain for all to use freely and without restrictions.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=File:Big-soft-brush.png&amp;diff=7107</id>
		<title>File:Big-soft-brush.png</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=File:Big-soft-brush.png&amp;diff=7107"/>
				<updated>2008-05-10T09:43:25Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: A sample brush file, which i release into public domain for all to use freely and without restrictions.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A sample brush file, which i release into public domain for all to use freely and without restrictions.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Dev:Sound_Layer&amp;diff=7050</id>
		<title>Dev:Sound Layer</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Dev:Sound_Layer&amp;diff=7050"/>
				<updated>2008-05-01T18:09:14Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Sound Layer */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;(This is a discussion page. If the sound is finally implemented in this way, the content of&lt;br /&gt;
 this page should go to the &amp;quot;Discuss this page&amp;quot; area and the layer description to replace it.)&lt;br /&gt;
==Introduction==&lt;br /&gt;
&lt;br /&gt;
As it has been reported in the [http://synfig.org/FAQ#Why_can.27t_I_get_sound_to_work.3F FAQ] section, the sound is not enabled for the moment in Synfig neither in Synfig Studio.&lt;br /&gt;
&lt;br /&gt;
The main reasons for that seems to be due to the fact that the current code lies in a sound library called FMOD (its current code is disabled in the linux version) and that it has not correspondence code to windows version. (I don't know if Mac version have any).&lt;br /&gt;
&lt;br /&gt;
As pabs commented in the IRC channel, synfig wouldn't be distributable if linked to FMOD libraries. Probably the [http://www.fmod.org/index.php/sales FMOD license] is not compatible with GPL Synfig license.&lt;br /&gt;
&lt;br /&gt;
 00:17 &amp;lt; pabs3&amp;gt; for the sound stuff, we do need to figure out what sound code &lt;br /&gt;
 we have atm, and figure which sound playback api to use. I'm thinking gstreamer&lt;br /&gt;
 or openal maybe&lt;br /&gt;
 00:18 &amp;lt; pabs3&amp;gt; synfig linked to fmod would not be distributable&lt;br /&gt;
&lt;br /&gt;
Said that, and assuming that a sound interface is implemented in the future inside synfig &amp;amp; synfigstudio (using gstreamer libraries for example), this wiki page wants to assert some regular animator user needs for the interface and behavior of the sound system in Synfig &amp;amp; Synfig Studio.&lt;br /&gt;
&lt;br /&gt;
==Sound Layer==&lt;br /&gt;
&lt;br /&gt;
Then main idea is that the sound can be inserted into the animation like any of the other layers. Here are some rules that the Sound Layer should meet:&lt;br /&gt;
&lt;br /&gt;
# A Synfig document can have several Sound Layers. &lt;br /&gt;
# Each sound Layer must have one sound file associated (and only one). The associated sound file is and remains external to the sif file. It means that it is not possible to carry with the sound in a single file (almost with the current sif file format) so they work like external image files. Anyway the sound file reference can be animatable. It means that you can change the sound file by the time. This would allow use several portions of recorded voices without need to make a whole record in a single file.&lt;br /&gt;
# The Sound Layer scope is the canvas, exactly the same as any other layer in Synfig. It means that when you import a sif file into other sif file it should carry its own sound refereced files. Also opening a canvas in its own window and play it would produce only the sounds that are inside that canvas.&lt;br /&gt;
#The parameters of the Sound Layer ca be those:&lt;br /&gt;
#* Frequency Gain: Default to be 1.0. It is the gain of frequency relative to of the original sound file frequency. If the Frequency Gain is bigger than 1.0 then the file is played at more speed that its natural frequency. If the Frequency Gain is lower than 1.0 the file is played a lower speed. (This is not needed as this can be achieved using the Time Loop Layer as described below --[[User:Dmd|Dmd]] 15:37, 8 February 2008 (EST))&lt;br /&gt;
#* Volume Gain: default to be 1.0. That's a filter value to increase or decrease the sound level of the sound file. It will be used to fade in/out the sounds and to perform sound mixing. Volumen Gain = 0 means to mute the sound layer. (This maps naturally to the layer Amount property, which could be renamed though for the Sound Layer. On the other hand due to the logarithmic nature of volume there may in fact be a gain parameter, but with 0 default, comparable to zoom. --[[User:Dmd|Dmd]] 05:23, 9 February 2008 (EST))&lt;br /&gt;
#* Start Time: Default to be 0f. It is the internal start time of the sound file. Maybe someone can think on a Duration parameter or an End Time parameter. Take in consideration that the whole sound file should be explored to know what's the file length or its duration. To change Duration of the sound use the Time Loop Layer on top of it.&lt;br /&gt;
#* Channel: This parameter tells to the mixer where to blend the sound with the rest of the sound layers. It should be a real number. For normal stereo system 0.0 means both speakers at same level. A value of 1.0 would mean right speaker and a value of -1.0 the left one. It can be extended to more channels but for the moment I don't know how to set up the numbers (have you any suggestion?). Maybe it can be a list of channles and the gain value for each one. The number of channels should be taken from the general options of the file. (I'd prefer position, as described next --[[User:Dmd|Dmd]] 15:37, 8 February 2008 (EST))&lt;br /&gt;
#* Position: A 2D (or even 3D) vector describing the position of the sound source. This can be animated in a natural (visible) way, linked etc. The sound engine will render the sound into whatever audio format it supports. It would also be able to render Doppler effects depending on the speed of movement.&lt;br /&gt;
# Sound layer doesn't produce any visual render. Also Sound Layer is not affected by any other Layer with following exceptions:&lt;br /&gt;
#* Time Loop Layer: This layer would affect to the Sound Layer. It would produce the same effect as it produce to a visual layer. Loop from Link Time to Destination time a duration of Duration. See Time Loop for more details. Can be used to produce repeteable music loops, to speed up or down the sound or even to reverse it. It depends on the Time Loop parameters and its waypoints or convert types.&lt;br /&gt;
#* Duplicate Layer: This layer would affect to the Sound Layer too. It would produce a duplicated of the Sound Layer like any other existing layer. Can be used to produce echoes or other nice effects.&lt;br /&gt;
#* Paste Canvas Layer: When a Sound layer is inside a Paste Canvas Layer it is affected by its Offset Time. The effect is the same as for any other layer inside the Paste Canvas Layer. The Zoom parameter can affect also to the Sound Layer by increasing or decreasing its Volume Gain paramter from its Value Base. (the zoom thing sounds unintuitive to me, see paramer Position for an alternative to be zoomed --[[User:Dmd|Dmd]] 15:37, 8 February 2008 (EST))&lt;br /&gt;
# The graph panel should display the current sound wave (after apply all the rest of modifier parameters when the file parameter is selected. It would allow sync animations to sounds.&lt;br /&gt;
&lt;br /&gt;
Exactly as there are video effect layers (e. g. [[Blur Layer]]), sophisticated sound effect layers can be added to manipulate a plain Sound Layer. Ideas:&lt;br /&gt;
* Frequency Filter Layer&lt;br /&gt;
* Reverb Layer&lt;br /&gt;
&lt;br /&gt;
Please feel free to add comments or more things to this feature request page. It is UNDER CONSTRUCTION ;)&lt;br /&gt;
&lt;br /&gt;
I would like to have the ability to extract values out of a sound file, which enable to make the light / brightness pulse with the same intensity like the volume of the music / sounds. This could be made with an external program, which extracts the time/volume levels into a csv-file, which can be read in by synfig. I need only make the brightness of my picture or single colors of this layer in synfigstudio  a placeholder, which can take the (8bit) csv-values at render time. disco! --[[User:SvH|SvH]] 14:09, 1 May 2008 (EDT)&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Categorical_Help&amp;diff=6996</id>
		<title>Categorical Help</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Categorical_Help&amp;diff=6996"/>
				<updated>2008-04-28T08:14:12Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Introduction */ typo&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
* [[Features]]&lt;br /&gt;
* [[Overview]]&lt;br /&gt;
* [[License]]&lt;br /&gt;
* [[Download]]&lt;br /&gt;
* Building Synfig:&lt;br /&gt;
** [[Build instructions]]&lt;br /&gt;
** [[Gentoo Ebuilds]]&lt;br /&gt;
** [[Mingw_installation]]&lt;br /&gt;
** [[Windows build instructions]]&lt;br /&gt;
** [[Subversion]]&lt;br /&gt;
* [[Gallery]]&lt;br /&gt;
* [[Communication]]&lt;br /&gt;
&lt;br /&gt;
== Synfig Studio Interface ==&lt;br /&gt;
&lt;br /&gt;
* The Main Canvas&lt;br /&gt;
** [[New Canvas Dialog|Canvas Properties]]&lt;br /&gt;
** [[Canvas Menu Caret]]&lt;br /&gt;
* [[Toolbox|The Toolbox]]&lt;br /&gt;
** [[Normal Tool]]&lt;br /&gt;
** [[Smooth Move Tool]]&lt;br /&gt;
** [[Scale Tool]]&lt;br /&gt;
** [[Rotate Tool]]&lt;br /&gt;
** [[Bline Tool]] ''(see also [[Creating Shapes]])''&lt;br /&gt;
** [[Polygon Tool]]&lt;br /&gt;
** [[Circle Tool]]&lt;br /&gt;
** [[Rectangle Tool]]&lt;br /&gt;
** [[Draw tool|Draw Tool]]&lt;br /&gt;
** [[Sketch Tool]]&lt;br /&gt;
** [[Eyedrop Tool]]&lt;br /&gt;
** [[Fill Tool]]&lt;br /&gt;
** [[Width tool|Width Tool]]&lt;br /&gt;
** [[Gradient Tool]]&lt;br /&gt;
** [[Zoom Tool]]&lt;br /&gt;
** [[Mirror Tool]]&lt;br /&gt;
* Dockable Dialogs - These are the main ancillary windows you'll use in Synfig to manage your project data outside of the canvas window.&lt;br /&gt;
** [[Tool Options Panel]]&lt;br /&gt;
** [[History Panel]]&lt;br /&gt;
** [[Canvas Browser Panel]]&lt;br /&gt;
** [[Keyframes Panel]]&lt;br /&gt;
** [[Layers Panel]]&lt;br /&gt;
** [[Params Panel]]&lt;br /&gt;
** [[Canvas MetaData Panel]]&lt;br /&gt;
** [[Children Panel]]&lt;br /&gt;
** [[Info Panel]]&lt;br /&gt;
** [[Navigator Panel]]&lt;br /&gt;
** [[Timetrack Panel]]&lt;br /&gt;
** [[Curves Panel]]&lt;br /&gt;
** [[Groups Panel]]&lt;br /&gt;
** [[Palette Editor Panel]]&lt;br /&gt;
* Dialogs&lt;br /&gt;
** [[Color Editor Dialog]]&lt;br /&gt;
** [[Gradient Editor Dialog]]&lt;br /&gt;
** [[Palette Browser]]&lt;br /&gt;
&lt;br /&gt;
==Working With Layers and Canvases ==&lt;br /&gt;
&lt;br /&gt;
* [[Layer|Introduction to layers and layer types]] &lt;br /&gt;
* [[Encapsulate|Encapsulation]]&lt;br /&gt;
* Layer Compositing - the [[Blend Method]] attribute.&lt;br /&gt;
* [[Sub-Canvases]]&lt;br /&gt;
* [[ListImporter]]&lt;br /&gt;
&lt;br /&gt;
==Animation==&lt;br /&gt;
&lt;br /&gt;
Anyone want to help out with the animations?&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Dev:Contribute_to_Code&amp;diff=6995</id>
		<title>Dev:Contribute to Code</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Dev:Contribute_to_Code&amp;diff=6995"/>
				<updated>2008-04-28T07:16:59Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /*Getting the source */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Code]]&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
You should know by the [[History|history]], that this program was initially written by an animation company, [[History|Voria Studios]]. Since the code of Synfig was released under [[License|GPL licence]] and turned into an open source project, there have been made some modifications to the code, which allows you to remove bugs and to add some new functionality. &lt;br /&gt;
&lt;br /&gt;
The only documentation you can get, is the source-code itself and the automatically generated [http://synfig.org/api/ API docs] by [http://www.doxygen.org doxygen].&lt;br /&gt;
This page tries to collect all the knowledge acquired by the current developers and to create typical guides for common tasks which would allow you to add new features and make the program grow. &lt;br /&gt;
&lt;br /&gt;
Feel free to add here all the information you can get from the experience of reading and modifying the source code or simply add your request to get more details from coders more familiar with the source. Hopefully they will be able to tell you, how it works and where to dive in.&lt;br /&gt;
&lt;br /&gt;
== Common tasks ==&lt;br /&gt;
&lt;br /&gt;
* Write a (brief) man page for synfigstudio.&lt;br /&gt;
* Expand the stub at [[wikipedia:synfig|wikipedia]] or translate it into your language.&lt;br /&gt;
* [[Source:Adding a Layer|Adding Layers to Synfig]]: this guide aids you to understand, how the layers work and how to add a new layer type.&lt;br /&gt;
* [[Source:Adding a Panel-Part I| Adding Panels to Synfigstudio]]: This guide explains, how to add a new panel and the objects on it.&lt;br /&gt;
&lt;br /&gt;
== Things you want to know about the code ==&lt;br /&gt;
&lt;br /&gt;
* Please add here a brief description of the things you want to know about the code and how to accomplish some task. Someone else will surely know it, and can help you to start developing on synfig.&lt;br /&gt;
&lt;br /&gt;
* Is there anywhere any kind of overview? Any sort of brief description of what each program does/is? Is synfigstudio the GUI for synfig? What's the ETL?&lt;br /&gt;
&lt;br /&gt;
==Documenting the code ==&lt;br /&gt;
&lt;br /&gt;
It would be a good thing, if all the code documentation and what is being discovered were confirmed and inserted directly in the source code itself. This would allow [http://www.doxygen.org doxygen] to generate the [http://synfig.org/api/ API docs] easily. &lt;br /&gt;
&lt;br /&gt;
Please follow these [http://www.stack.nl/~dimitri/doxygen/docblocks.html doxygen rules] to add documentation to the source code.&lt;br /&gt;
&lt;br /&gt;
==Getting the source==&lt;br /&gt;
We use SVN to store all our sources. To check out the core part, you have to issue this command on your console:&lt;br /&gt;
&lt;br /&gt;
 svn co http://svn.voria.com/code/synfig-core/trunk/ synfig-core&lt;br /&gt;
&lt;br /&gt;
If you have installed a svn-client on your computer, you will get all important sources in a new created subfolder ''synfig-core'', from where you have issued the above command.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Dev:Contribute_to_Code&amp;diff=6994</id>
		<title>Dev:Contribute to Code</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Dev:Contribute_to_Code&amp;diff=6994"/>
				<updated>2008-04-28T06:26:14Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Common tasks */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Code]]&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
You should know by the [[History|history]], that this program was initially written by an animation company, [[History|Voria Studios]]. Since the code of Synfig was released under [[License|GPL licence]] and turned into an open source project, there have been made some modifications to the code, which allows you to remove bugs and to add some new functionality. &lt;br /&gt;
&lt;br /&gt;
The only documentation you can get, is the source-code itself and the automatically generated [http://synfig.org/api/ API docs] by [http://www.doxygen.org doxygen].&lt;br /&gt;
This page tries to collect all the knowledge acquired by the current developers and to create typical guides for common tasks which would allow you to add new features and make the program grow. &lt;br /&gt;
&lt;br /&gt;
Feel free to add here all the information you can get from the experience of reading and modifying the source code or simply add your request to get more details from coders more familiar with the source. Hopefully they will be able to tell you, how it works and where to dive in.&lt;br /&gt;
&lt;br /&gt;
== Common tasks ==&lt;br /&gt;
&lt;br /&gt;
* Write a (brief) man page for synfigstudio.&lt;br /&gt;
* Expand the stub at [[wikipedia:synfig|wikipedia]] or translate it into your language.&lt;br /&gt;
* [[Source:Adding a Layer|Adding Layers to Synfig]]: this guide aids you to understand, how the layers work and how to add a new layer type.&lt;br /&gt;
* [[Source:Adding a Panel-Part I| Adding Panels to Synfigstudio]]: This guide explains, how to add a new panel and the objects on it.&lt;br /&gt;
&lt;br /&gt;
== Things you want to know about the code ==&lt;br /&gt;
&lt;br /&gt;
* Please add here a brief description of the things you want to know about the code and how to accomplish some task. Someone else will surely know it, and can help you to start developing on synfig.&lt;br /&gt;
&lt;br /&gt;
* Is there anywhere any kind of overview? Any sort of brief description of what each program does/is? Is synfigstudio the GUI for synfig? What's the ETL?&lt;br /&gt;
&lt;br /&gt;
==Documenting the code ==&lt;br /&gt;
&lt;br /&gt;
It would be a good thing, if all the code documentation and what is being discovered were confirmed and inserted directly in the source code itself. This would allow [http://www.doxygen.org doxygen] to generate the [http://synfig.org/api/ API docs] easily. &lt;br /&gt;
&lt;br /&gt;
Please follow these [http://www.stack.nl/~dimitri/doxygen/docblocks.html doxygen rules] to add documentation to the source code.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Dev:Contribute_to_Code&amp;diff=6993</id>
		<title>Dev:Contribute to Code</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Dev:Contribute_to_Code&amp;diff=6993"/>
				<updated>2008-04-28T06:15:16Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: /* Common tasks */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Code]]&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
You should know by the [[History|history]], that this program was initially written by an animation company, [[History|Voria Studios]]. Since the code of Synfig was released under [[License|GPL licence]] and turned into an open source project, there have been made some modifications to the code, which allows you to remove bugs and to add some new functionality. &lt;br /&gt;
&lt;br /&gt;
The only documentation you can get, is the source-code itself and the automatically generated [http://synfig.org/api/ API docs] by [http://www.doxygen.org doxygen].&lt;br /&gt;
This page tries to collect all the knowledge acquired by the current developers and to create typical guides for common tasks which would allow you to add new features and make the program grow. &lt;br /&gt;
&lt;br /&gt;
Feel free to add here all the information you can get from the experience of reading and modifying the source code or simply add your request to get more details from coders more familiar with the source. Hopefully they will be able to tell you, how it works and where to dive in.&lt;br /&gt;
&lt;br /&gt;
== Common tasks ==&lt;br /&gt;
&lt;br /&gt;
* Write a (brief) man page for synfigstudio.&lt;br /&gt;
* [[Source:Adding a Layer|Adding Layers to Synfig]]: this guide aids you to understand, how the layers work and how to add a new layer type.&lt;br /&gt;
* [[Source:Adding a Panel-Part I| Adding Panels to Synfigstudio]]: This guide explains, how to add a new panel and the objects on it.&lt;br /&gt;
&lt;br /&gt;
== Things you want to know about the code ==&lt;br /&gt;
&lt;br /&gt;
* Please add here a brief description of the things you want to know about the code and how to accomplish some task. Someone else will surely know it, and can help you to start developing on synfig.&lt;br /&gt;
&lt;br /&gt;
* Is there anywhere any kind of overview? Any sort of brief description of what each program does/is? Is synfigstudio the GUI for synfig? What's the ETL?&lt;br /&gt;
&lt;br /&gt;
==Documenting the code ==&lt;br /&gt;
&lt;br /&gt;
It would be a good thing, if all the code documentation and what is being discovered were confirmed and inserted directly in the source code itself. This would allow [http://www.doxygen.org doxygen] to generate the [http://synfig.org/api/ API docs] easily. &lt;br /&gt;
&lt;br /&gt;
Please follow these [http://www.stack.nl/~dimitri/doxygen/docblocks.html doxygen rules] to add documentation to the source code.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Dev:Valgrind&amp;diff=6988</id>
		<title>Dev:Valgrind</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Dev:Valgrind&amp;diff=6988"/>
				<updated>2008-04-27T11:26:50Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: New page: I made a leak check with valgrind on Synfig Studio 0.61.08. Here is just the beginning of the output, because it is too much. The most important (serious) parts are on the top anyway.   [c...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;I made a leak check with valgrind on Synfig Studio 0.61.08. Here is just the beginning of the output, because it is too much.&lt;br /&gt;
The most important (serious) parts are on the top anyway.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[code]&lt;br /&gt;
stefan@cipy:~$ valgrind --leak-check=full synfigstudio&lt;br /&gt;
==9302== Memcheck, a memory error detector.&lt;br /&gt;
==9302== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al.&lt;br /&gt;
==9302== Using LibVEX rev 1658, a library for dynamic binary translation.&lt;br /&gt;
==9302== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP.&lt;br /&gt;
==9302== Using valgrind-3.2.1-Debian, a dynamic binary instrumentation framework.&lt;br /&gt;
==9302== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al.&lt;br /&gt;
==9302== For more details, rerun with: -v&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014759: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4005B69: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4007995: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53390A1: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x5339254: __libc_dlopen_mode (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x531445E: __nss_lookup_function (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x531454F: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x53162B5: __nss_passwd_lookup (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==  Address 0x549B8FC is 36 bytes inside a block of size 38 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4007F33: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53390A1: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x5339254: __libc_dlopen_mode (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x531445E: __nss_lookup_function (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x531454F: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x53162B5: __nss_passwd_lookup (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x52C2D6D: getpwnam_r (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014787: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4005B69: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4007995: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400B836: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400BA2A: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010DF4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53390A1: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x5339254: __libc_dlopen_mode (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==  Address 0x549BC44 is 28 bytes inside a block of size 31 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4007F33: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400B836: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400BA2A: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010DF4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53390A1: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x5339254: __libc_dlopen_mode (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x531445E: __nss_lookup_function (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014743: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4005B69: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4007995: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53390A1: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x5339254: __libc_dlopen_mode (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x531445E: __nss_lookup_function (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x4395F0B: (within /lib/tls/i686/cmov/libnss_compat-2.5.so)&lt;br /&gt;
==9302==    by 0x4397422: _nss_compat_getpwnam_r (in /lib/tls/i686/cmov/libnss_compat-2.5.so)&lt;br /&gt;
==9302==  Address 0x549C2F0 is 32 bytes inside a block of size 35 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4007F33: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53390A1: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x5339254: __libc_dlopen_mode (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x531445E: __nss_lookup_function (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x4395F0B: (within /lib/tls/i686/cmov/libnss_compat-2.5.so)&lt;br /&gt;
==9302==    by 0x4397422: _nss_compat_getpwnam_r (in /lib/tls/i686/cmov/libnss_compat-2.5.so)&lt;br /&gt;
==9302==    by 0x52C2C92: getpwnam_r (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014759: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4005B69: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4007995: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400B836: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400BA2A: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010DF4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53390A1: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x5339254: __libc_dlopen_mode (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==  Address 0x549C63C is 36 bytes inside a block of size 37 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4007F33: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400B836: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400BA2A: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010DF4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53390A1: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x5339254: __libc_dlopen_mode (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x531445E: __nss_lookup_function (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
&lt;br /&gt;
   synfig studio -- starting up application...&lt;br /&gt;
&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Syscall param writev(vector[...]) points to uninitialised byte(s)&lt;br /&gt;
==9302==    at 0x40007F2: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x545C302: (within /usr/lib/libxcb.so.1.0.0)&lt;br /&gt;
==9302==    by 0x545C89A: (within /usr/lib/libxcb.so.1.0.0)&lt;br /&gt;
==9302==    by 0x545C9CC: (within /usr/lib/libxcb.so.1.0.0)&lt;br /&gt;
==9302==    by 0x545CB1E: xcb_flush (in /usr/lib/libxcb.so.1.0.0)&lt;br /&gt;
==9302==    by 0x4F89DDD: _XSend (in /usr/lib/libX11.so.6.2.0)&lt;br /&gt;
==9302==    by 0x4F7792A: XQueryExtension (in /usr/lib/libX11.so.6.2.0)&lt;br /&gt;
==9302==    by 0x4F6C6BA: XInitExtension (in /usr/lib/libX11.so.6.2.0)&lt;br /&gt;
==9302==    by 0x4E94DFF: XFixesFindDisplay (in /usr/lib/libXfixes.so.3.1.0)&lt;br /&gt;
==9302==    by 0x4E9509C: XFixesQueryExtension (in /usr/lib/libXfixes.so.3.1.0)&lt;br /&gt;
==9302==    by 0x4DAF3C4: gdk_display_open (in /usr/lib/libgdk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4D8CCFE: gdk_display_open_default_libgtk_only (in /usr/lib/libgdk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==  Address 0x54F2C14 is 4,684 bytes inside a block of size 8,556 alloc'd&lt;br /&gt;
==9302==    at 0x401F95F: calloc (vg_replace_malloc.c:279)&lt;br /&gt;
==9302==    by 0x545C510: xcb_connect_to_fd (in /usr/lib/libxcb.so.1.0.0)&lt;br /&gt;
==9302==    by 0x545EBF8: xcb_connect (in /usr/lib/libxcb.so.1.0.0)&lt;br /&gt;
==9302==    by 0x4F88E9F: _XConnectXCB (in /usr/lib/libX11.so.6.2.0)&lt;br /&gt;
==9302==    by 0x4F71A28: XOpenDisplay (in /usr/lib/libX11.so.6.2.0)&lt;br /&gt;
==9302==    by 0x4DAF211: gdk_display_open (in /usr/lib/libgdk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4D8CCFE: gdk_display_open_default_libgtk_only (in /usr/lib/libgdk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4AC360E: gtk_init_check (in /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4AC3643: gtk_init (in /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x47A17A6: Gtk::Main::init(int*, char***, bool) (in /usr/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9302==    by 0x47A18AB: Gtk::Main::Main(int*, char***, bool) (in /usr/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9302==    by 0x81E5F06: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x40145E1: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C5D8: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4E1F0C2: _gdk_pixbuf_load_module (in /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4E1FFC1: gdk_pixbuf_new_from_file (in /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4BEABB4: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4BEB6C1: gtk_window_set_default_icon_from_file (in /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==  Address 0x56D503C is 52 bytes inside a block of size 55 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x50B62C5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x50C9878: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x506C8E2: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4E1F0C2: _gdk_pixbuf_load_module (in /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4E1FFC1: gdk_pixbuf_new_from_file (in /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4BEABB4: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4BEB6C1: gtk_window_set_default_icon_from_file (in /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x482B4AC: Gtk::Window::set_default_icon_from_file(std::string const&amp;amp;) (in /usr/lib/libgtkmm-2.4.so.1.&lt;br /&gt;
0.30)&lt;br /&gt;
==9302==    by 0x826861C: studio::IconController::IconController(std::string const&amp;amp;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==    by 0x81E5FAD: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x40145E1: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40078D9: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C5D8: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4E1F0C2: _gdk_pixbuf_load_module (in /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4E1FFC1: gdk_pixbuf_new_from_file (in /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11)&lt;br /&gt;
==9302==  Address 0x56D503C is 52 bytes inside a block of size 55 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x50B62C5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x50C9878: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x506C8E2: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4E1F0C2: _gdk_pixbuf_load_module (in /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4E1FFC1: gdk_pixbuf_new_from_file (in /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4BEABB4: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4BEB6C1: gtk_window_set_default_icon_from_file (in /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x482B4AC: Gtk::Window::set_default_icon_from_file(std::string const&amp;amp;) (in /usr/lib/libgtkmm-2.4.so.1.&lt;br /&gt;
0.30)&lt;br /&gt;
==9302==    by 0x826861C: studio::IconController::IconController(std::string const&amp;amp;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==    by 0x81E5FAD: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014759: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40078D9: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C5D8: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4E1F0C2: _gdk_pixbuf_load_module (in /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4E1FFC1: gdk_pixbuf_new_from_file (in /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11)&lt;br /&gt;
==9302==  Address 0x56D503C is 52 bytes inside a block of size 55 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x50B62C5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x50C9878: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x506C8E2: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4E1F0C2: _gdk_pixbuf_load_module (in /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4E1FFC1: gdk_pixbuf_new_from_file (in /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4BEABB4: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4BEB6C1: gtk_window_set_default_icon_from_file (in /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x482B4AC: Gtk::Window::set_default_icon_from_file(std::string const&amp;amp;) (in /usr/lib/libgtkmm-2.4.so.1.&lt;br /&gt;
0.30)&lt;br /&gt;
==9302==    by 0x826861C: studio::IconController::IconController(std::string const&amp;amp;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==    by 0x81E5FAD: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014759: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400D2A9: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4009812: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53393D2: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x5339639: _dl_sym (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x506EDE7: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506ED72: dlsym (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C1BC: g_module_symbol (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x506C6C4: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4E1F0C2: _gdk_pixbuf_load_module (in /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11)&lt;br /&gt;
==9302==  Address 0x56D50EC is 52 bytes inside a block of size 55 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4006EB4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40078D9: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C5D8: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4E1F0C2: _gdk_pixbuf_load_module (in /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014618: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C5D8: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8B091: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x505C9E7: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8AF78: gtk_theme_engine_get (in /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0C82F: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==  Address 0x5744730 is 40 bytes inside a block of size 43 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x50B62C5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x50C9878: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x506C8E2: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8B091: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x505C9E7: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8AF78: gtk_theme_engine_get (in /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0C82F: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0EFB2: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0FAE9: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0FF21: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B100DC: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014618: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40078D9: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C5D8: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8B091: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x505C9E7: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9302==  Address 0x5744730 is 40 bytes inside a block of size 43 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x50B62C5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x50C9878: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x506C8E2: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8B091: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x505C9E7: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8AF78: gtk_theme_engine_get (in /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0C82F: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0EFB2: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0FAE9: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0FF21: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B100DC: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014770: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40078D9: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C5D8: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8B091: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x505C9E7: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9302==  Address 0x5744730 is 40 bytes inside a block of size 43 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x50B62C5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x50C9878: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x506C8E2: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8B091: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x505C9E7: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8AF78: gtk_theme_engine_get (in /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0C82F: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0EFB2: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0FAE9: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0FF21: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B100DC: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014770: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4005B69: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4007995: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C5D8: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8B091: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==  Address 0x5744730 is 40 bytes inside a block of size 43 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x50B62C5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x50C9878: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x506C8E2: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8B091: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x505C9E7: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8AF78: gtk_theme_engine_get (in /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0C82F: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0EFB2: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0FAE9: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B0FF21: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4B100DC: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014770: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400D2A9: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4009812: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53393D2: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x5339639: _dl_sym (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x506EDE7: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506ED72: dlsym (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C1BC: g_module_symbol (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x506C6E5: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8B091: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==  Address 0x5744790 is 40 bytes inside a block of size 43 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4006EB4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40078D9: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C5D8: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4B8B091: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014647: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C5D8: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA7FB0: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x505C9E7: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA810A: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EA8206: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==  Address 0x57A2EC4 is 44 bytes inside a block of size 47 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x50B62C5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x50C9878: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x506C8E2: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA7FB0: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x505C9E7: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA810A: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EA8206: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EA8285: pango_map_get_engines (in /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EABD24: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EABF21: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EAC591: pango_itemize_with_base_dir (in /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014647: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40078D9: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C5D8: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA7FB0: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x505C9E7: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9302==  Address 0x57A2EC4 is 44 bytes inside a block of size 47 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x50B62C5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x50C9878: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x506C8E2: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA7FB0: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x505C9E7: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA810A: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EA8206: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EA8285: pango_map_get_engines (in /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EABD24: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EABF21: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EAC591: pango_itemize_with_base_dir (in /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014787: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40078D9: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C5D8: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA7FB0: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x505C9E7: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9302==  Address 0x57A2EC4 is 44 bytes inside a block of size 47 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x50B62C5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x50C9878: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x506C8E2: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA7FB0: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x505C9E7: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA810A: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EA8206: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EA8285: pango_map_get_engines (in /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EABD24: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EABF21: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EAC591: pango_itemize_with_base_dir (in /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014787: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4005B69: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4007995: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C5D8: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA7FB0: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==  Address 0x57A2EC4 is 44 bytes inside a block of size 47 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x50B62C5: g_malloc (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x50C9878: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x506C8E2: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA7FB0: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x505C9E7: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA810A: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EA8206: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EA8285: pango_map_get_engines (in /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EABD24: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EABF21: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==    by 0x4EAC591: pango_itemize_with_base_dir (in /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014787: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400D2A9: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4009812: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53393D2: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x5339639: _dl_sym (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x506EDE7: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506ED72: dlsym (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C1BC: g_module_symbol (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x506C6C4: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA7FB0: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==  Address 0x588DFC4 is 44 bytes inside a block of size 47 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4006EB4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40078D9: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506C5D8: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1200.11)&lt;br /&gt;
==9302==    by 0x4EA7FB0: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014787: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4007053: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400760F: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4007CF6: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400B836: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400BA2A: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010DF4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==  Address 0x59A68F4 is 12 bytes inside a block of size 15 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4006EB4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4006FE5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400760F: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4007CF6: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400B836: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400BA2A: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010DF4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014770: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4005B69: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4007995: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400B836: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400BA2A: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010DF4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==  Address 0x59580A0 is 24 bytes inside a block of size 26 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4007F33: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400B836: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400BA2A: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010DF4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014743: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4005B69: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4007995: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400B836: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400BA2A: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010DF4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==  Address 0x5958C28 is 16 bytes inside a block of size 19 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4007F33: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400B836: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400BA2A: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010DF4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Conditional jump or move depends on uninitialised value(s)&lt;br /&gt;
==9302==    at 0x401474C: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53393D2: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x5339639: _dl_sym (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x506EDE7: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506ED72: dlsym (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A48B: sys_dl_sym (ltdl.c:1138)&lt;br /&gt;
==9302==    by 0x4348828: lt_dlsym (ltdl.c:3935)&lt;br /&gt;
==9302==    by 0x43106A2: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014743: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400D2A9: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4009812: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53393D2: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x5339639: _dl_sym (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x506EDE7: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506ED72: dlsym (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A48B: sys_dl_sym (ltdl.c:1138)&lt;br /&gt;
==9302==    by 0x4348828: lt_dlsym (ltdl.c:3935)&lt;br /&gt;
==9302==    by 0x43106A2: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==  Address 0x59A7760 is 48 bytes inside a block of size 49 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4006EB4: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40078D9: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A56C: sys_dl_open (ltdl.c:1106)&lt;br /&gt;
==9302==    by 0x434801F: tryall_dlopen (ltdl.c:2453)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Conditional jump or move depends on uninitialised value(s)&lt;br /&gt;
==9302==    at 0x401477A: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53393D2: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x5339639: _dl_sym (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x506EDE7: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506ED72: dlsym (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A48B: sys_dl_sym (ltdl.c:1138)&lt;br /&gt;
==9302==    by 0x4348828: lt_dlsym (ltdl.c:3935)&lt;br /&gt;
==9302==    by 0x4310A72: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Conditional jump or move depends on uninitialised value(s)&lt;br /&gt;
==9302==    at 0x4014785: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53393D2: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x5339639: _dl_sym (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x506EDE7: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506ED72: dlsym (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A48B: sys_dl_sym (ltdl.c:1138)&lt;br /&gt;
==9302==    by 0x4348828: lt_dlsym (ltdl.c:3935)&lt;br /&gt;
==9302==    by 0x4310A72: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Conditional jump or move depends on uninitialised value(s)&lt;br /&gt;
==9302==    at 0x4014763: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53393D2: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x5339639: _dl_sym (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x506EDE7: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506ED72: dlsym (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A48B: sys_dl_sym (ltdl.c:1138)&lt;br /&gt;
==9302==    by 0x4348828: lt_dlsym (ltdl.c:3935)&lt;br /&gt;
==9302==    by 0x4310A72: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Conditional jump or move depends on uninitialised value(s)&lt;br /&gt;
==9302==    at 0x401476E: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53393D2: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x5339639: _dl_sym (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x506EDE7: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506ED72: dlsym (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A48B: sys_dl_sym (ltdl.c:1138)&lt;br /&gt;
==9302==    by 0x4348828: lt_dlsym (ltdl.c:3935)&lt;br /&gt;
==9302==    by 0x4310A72: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Conditional jump or move depends on uninitialised value(s)&lt;br /&gt;
==9302==    at 0x4014791: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53393D2: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x5339639: _dl_sym (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x506EDE7: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506ED72: dlsym (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A48B: sys_dl_sym (ltdl.c:1138)&lt;br /&gt;
==9302==    by 0x4348828: lt_dlsym (ltdl.c:3935)&lt;br /&gt;
==9302==    by 0x4310A72: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Conditional jump or move depends on uninitialised value(s)&lt;br /&gt;
==9302==    at 0x401479C: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x53393D2: (within /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x5339639: _dl_sym (in /lib/tls/i686/cmov/libc-2.5.so)&lt;br /&gt;
==9302==    by 0x506EDE7: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506ED72: dlsym (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A48B: sys_dl_sym (ltdl.c:1138)&lt;br /&gt;
==9302==    by 0x4348828: lt_dlsym (ltdl.c:3935)&lt;br /&gt;
==9302==    by 0x4310A72: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x40145E1: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A56C: sys_dl_open (ltdl.c:1106)&lt;br /&gt;
==9302==    by 0x434801F: tryall_dlopen (ltdl.c:2453)&lt;br /&gt;
==9302==    by 0x43499A0: try_dlopen (ltdl.c:3404)&lt;br /&gt;
==9302==    by 0x434A38B: lt_dlopenext (ltdl.c:3542)&lt;br /&gt;
==9302==  Address 0x5ACDCB4 is 20 bytes inside a block of size 21 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4346C66: lt_emalloc (ltdl.c:1026)&lt;br /&gt;
==9302==    by 0x434A2EB: lt_dlopenext (ltdl.c:3506)&lt;br /&gt;
==9302==    by 0x43105B2: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==    by 0x81E65E6: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014759: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A56C: sys_dl_open (ltdl.c:1106)&lt;br /&gt;
==9302==    by 0x434801F: tryall_dlopen (ltdl.c:2453)&lt;br /&gt;
==9302==    by 0x43499A0: try_dlopen (ltdl.c:3404)&lt;br /&gt;
==9302==    by 0x434A38B: lt_dlopenext (ltdl.c:3542)&lt;br /&gt;
==9302==  Address 0x5ACDCB4 is 20 bytes inside a block of size 21 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4346C66: lt_emalloc (ltdl.c:1026)&lt;br /&gt;
==9302==    by 0x434A2EB: lt_dlopenext (ltdl.c:3506)&lt;br /&gt;
==9302==    by 0x43105B2: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==    by 0x81E65E6: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014759: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4008164: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A56C: sys_dl_open (ltdl.c:1106)&lt;br /&gt;
==9302==    by 0x434801F: tryall_dlopen (ltdl.c:2453)&lt;br /&gt;
==9302==    by 0x43499A0: try_dlopen (ltdl.c:3404)&lt;br /&gt;
==9302==  Address 0x5ACDCB4 is 20 bytes inside a block of size 21 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4346C66: lt_emalloc (ltdl.c:1026)&lt;br /&gt;
==9302==    by 0x434A2EB: lt_dlopenext (ltdl.c:3506)&lt;br /&gt;
==9302==    by 0x43105B2: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==    by 0x81E65E6: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x40145A3: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A56C: sys_dl_open (ltdl.c:1106)&lt;br /&gt;
==9302==    by 0x434801F: tryall_dlopen (ltdl.c:2453)&lt;br /&gt;
==9302==    by 0x43499A0: try_dlopen (ltdl.c:3404)&lt;br /&gt;
==9302==    by 0x434A38B: lt_dlopenext (ltdl.c:3542)&lt;br /&gt;
==9302==    by 0x431093E: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==  Address 0x5ACF038 is 16 bytes inside a block of size 18 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4346C66: lt_emalloc (ltdl.c:1026)&lt;br /&gt;
==9302==    by 0x434A2EB: lt_dlopenext (ltdl.c:3506)&lt;br /&gt;
==9302==    by 0x431093E: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==    by 0x81E65E6: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x40145A3: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A56C: sys_dl_open (ltdl.c:1106)&lt;br /&gt;
==9302==    by 0x434801F: tryall_dlopen (ltdl.c:2453)&lt;br /&gt;
==9302==    by 0x43499A0: try_dlopen (ltdl.c:3404)&lt;br /&gt;
==9302==    by 0x434A38B: lt_dlopenext (ltdl.c:3542)&lt;br /&gt;
==9302==  Address 0x5ACF038 is 16 bytes inside a block of size 18 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4346C66: lt_emalloc (ltdl.c:1026)&lt;br /&gt;
==9302==    by 0x434A2EB: lt_dlopenext (ltdl.c:3506)&lt;br /&gt;
==9302==    by 0x431093E: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==    by 0x81E65E6: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014743: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A56C: sys_dl_open (ltdl.c:1106)&lt;br /&gt;
==9302==    by 0x434801F: tryall_dlopen (ltdl.c:2453)&lt;br /&gt;
==9302==    by 0x43499A0: try_dlopen (ltdl.c:3404)&lt;br /&gt;
==9302==    by 0x434A38B: lt_dlopenext (ltdl.c:3542)&lt;br /&gt;
==9302==  Address 0x5ACF038 is 16 bytes inside a block of size 18 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4346C66: lt_emalloc (ltdl.c:1026)&lt;br /&gt;
==9302==    by 0x434A2EB: lt_dlopenext (ltdl.c:3506)&lt;br /&gt;
==9302==    by 0x431093E: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==    by 0x81E65E6: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014743: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4008164: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A56C: sys_dl_open (ltdl.c:1106)&lt;br /&gt;
==9302==    by 0x434801F: tryall_dlopen (ltdl.c:2453)&lt;br /&gt;
==9302==    by 0x43499A0: try_dlopen (ltdl.c:3404)&lt;br /&gt;
==9302==  Address 0x5ACF038 is 16 bytes inside a block of size 18 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x4346C66: lt_emalloc (ltdl.c:1026)&lt;br /&gt;
==9302==    by 0x434A2EB: lt_dlopenext (ltdl.c:3506)&lt;br /&gt;
==9302==    by 0x431093E: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==    by 0x81E65E6: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Invalid read of size 4&lt;br /&gt;
==9302==    at 0x4014743: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A56C: sys_dl_open (ltdl.c:1106)&lt;br /&gt;
==9302==    by 0x434801F: tryall_dlopen (ltdl.c:2453)&lt;br /&gt;
==9302==    by 0x43499A0: try_dlopen (ltdl.c:3404)&lt;br /&gt;
==9302==    by 0x434A38B: lt_dlopenext (ltdl.c:3542)&lt;br /&gt;
==9302==    by 0x431093E: synfig::Module::Register(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/&lt;br /&gt;
libsynfig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x430DCA1: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9302==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9302==  Address 0x5ACF920 is 48 bytes inside a block of size 49 alloc'd&lt;br /&gt;
==9302==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9302==    by 0x400D0B2: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4008164: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x4010D94: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x40108ED: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506EC2C: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x400CFA5: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x506F2AB: (within /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x506EB63: dlopen (in /lib/tls/i686/cmov/libdl-2.5.so)&lt;br /&gt;
==9302==    by 0x434A56C: sys_dl_open (ltdl.c:1106)&lt;br /&gt;
==9302==    by 0x434801F: tryall_dlopen (ltdl.c:2453)&lt;br /&gt;
==9302==&lt;br /&gt;
==9302== Syscall param writev(vector[...]) points to uninitialised byte(s)&lt;br /&gt;
==9302==    at 0x40007F2: (within /lib/ld-2.5.so)&lt;br /&gt;
==9302==    by 0x545C302: (within /usr/lib/libxcb.so.1.0.0)&lt;br /&gt;
==9302==    by 0x545C89A: (within /usr/lib/libxcb.so.1.0.0)&lt;br /&gt;
==9302==    by 0x545D0AF: xcb_send_request (in /usr/lib/libxcb.so.1.0.0)&lt;br /&gt;
==9302==    by 0x4F88885: _XPutXCBBuffer (in /usr/lib/libX11.so.6.2.0)&lt;br /&gt;
==9302==    by 0x4F88B9D: (within /usr/lib/libX11.so.6.2.0)&lt;br /&gt;
==9302==    by 0x4F76942: XPutImage (in /usr/lib/libX11.so.6.2.0)&lt;br /&gt;
==9302==    by 0x4E8BEFD: XcursorImageLoadCursor (in /usr/lib/libXcursor.so.1.0.2)&lt;br /&gt;
==9302==    by 0x4E8CBF7: XcursorImagesLoadCursor (in /usr/lib/libXcursor.so.1.0.2)&lt;br /&gt;
==9302==    by 0x4E90229: XcursorTryShapeCursor (in /usr/lib/libXcursor.so.1.0.2)&lt;br /&gt;
==9302==    by 0x4F605A1: XCreateGlyphCursor (in /usr/lib/libX11.so.6.2.0)&lt;br /&gt;
==9302==    by 0x4F60A2C: XCreateFontCursor (in /usr/lib/libX11.so.6.2.0)&lt;br /&gt;
==9302==  Address 0x54F2ADC is 4,372 bytes inside a block of size 8,556 alloc'd&lt;br /&gt;
==9302==    at 0x401F95F: calloc (vg_replace_malloc.c:279)&lt;br /&gt;
==9302==    by 0x545C510: xcb_connect_to_fd (in /usr/lib/libxcb.so.1.0.0)&lt;br /&gt;
==9302==    by 0x545EBF8: xcb_connect (in /usr/lib/libxcb.so.1.0.0)&lt;br /&gt;
==9302==    by 0x4F88E9F: _XConnectXCB (in /usr/lib/libX11.so.6.2.0)&lt;br /&gt;
==9302==    by 0x4F71A28: XOpenDisplay (in /usr/lib/libX11.so.6.2.0)&lt;br /&gt;
==9302==    by 0x4DAF211: gdk_display_open (in /usr/lib/libgdk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4D8CCFE: gdk_display_open_default_libgtk_only (in /usr/lib/libgdk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4AC360E: gtk_init_check (in /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x4AC3643: gtk_init (in /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9302==    by 0x47A17A6: Gtk::Main::init(int*, char***, bool) (in /usr/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9302==    by 0x47A18AB: Gtk::Main::Main(int*, char***, bool) (in /usr/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9302==    by 0x81E5F06: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
synfig(9302) [12:42:35] info: Entered Fill State&lt;br /&gt;
synfig(9302) [12:43:02] info: STATE FILL: Received layer clicked Event&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== ERROR SUMMARY: 141 errors from 39 contexts (suppressed: 316 from 1)&lt;br /&gt;
==9312== malloc/free: in use at exit: 9,219,658 bytes in 55,474 blocks.&lt;br /&gt;
==9312== malloc/free: 440,192 allocs, 384,718 frees, 83,551,300 bytes allocated.&lt;br /&gt;
==9312== For counts of detected errors, rerun with: -v&lt;br /&gt;
==9312== searching for pointers to 55,474 not-freed blocks.&lt;br /&gt;
==9312== checked 10,931,588 bytes.&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 2 bytes in 1 blocks are definitely lost in loss record 4 of 1,058&lt;br /&gt;
==9312==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9312==    by 0x4346C66: lt_emalloc (ltdl.c:1026)&lt;br /&gt;
==9312==    by 0x4347CF4: canonicalize_path (ltdl.c:2586)&lt;br /&gt;
==9312==    by 0x434833A: lt_dlpath_insertdir (ltdl.c:3992)&lt;br /&gt;
==9312==    by 0x4348690: lt_dladdsearchdir (ltdl.c:4059)&lt;br /&gt;
==9312==    by 0x430FF30: synfig::Module::subsys_init(std::string const&amp;amp;) (in /usr/local/lib/libsynfig.so.0.0.0)&lt;br /&gt;
==9312==    by 0x430D70F: synfig::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/libsyn&lt;br /&gt;
fig.so.0.0.0)&lt;br /&gt;
==9312==    by 0x415735C: synfigapp::Main::Main(std::string const&amp;amp;, synfig::ProgressCallback*) (in /usr/local/lib/lib&lt;br /&gt;
synfigapp.so.0.0.0)&lt;br /&gt;
==9312==    by 0x81E65E6: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 20 bytes in 1 blocks are possibly lost in loss record 65 of 1,058&lt;br /&gt;
==9312==    at 0x4020620: malloc (vg_replace_malloc.c:149)&lt;br /&gt;
==9312==    by 0x4E3F452: (within /usr/lib/libfontconfig.so.1.2.0)&lt;br /&gt;
==9312==    by 0x4E3F89B: FcConfigSubstituteWithPat (in /usr/lib/libfontconfig.so.1.2.0)&lt;br /&gt;
==9312==    by 0x4E4A929: FcFontRenderPrepare (in /usr/lib/libfontconfig.so.1.2.0)&lt;br /&gt;
==9312==    by 0x537D7E2: (within /usr/lib/libpangoft2-1.0.so.0.1600.2)&lt;br /&gt;
==9312==    by 0x4EAE25F: pango_font_map_load_fontset (in /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9312==    by 0x4EAC206: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9312==    by 0x4EAC591: pango_itemize_with_base_dir (in /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9312==    by 0x4EB4A1A: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9312==    by 0x4EB5646: (within /usr/lib/libpango-1.0.so.0.1600.2)&lt;br /&gt;
==9312==    by 0x4AB498F: (within /usr/lib/libgtk-x11-2.0.so.0.1000.11)&lt;br /&gt;
==9312==    by 0x481C989: Gtk::Widget_Class::size_request_callback(_GtkWidget*, _GtkRequisition*) (in /usr/lib/libgtk&lt;br /&gt;
mm-2.4.so.1.0.30)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 24 bytes in 1 blocks are possibly lost in loss record 73 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x474D0A5: Gtk::AccelGroup_Class::wrap_new(_GObject*) (in /usr/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9312==    by 0x4D5C252: (within /usr/lib/libglibmm-2.4.so.1.0.24)&lt;br /&gt;
==9312==    by 0x4D5C304: Glib::wrap_auto(_GObject*, bool) (in /usr/lib/libglibmm-2.4.so.1.0.24)&lt;br /&gt;
==9312==    by 0x474D48C: Glib::wrap(_GtkAccelGroup*, bool) (in /usr/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9312==    by 0x4818C34: Gtk::UIManager::get_accel_group() (in /usr/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9312==    by 0x82B4392: studio::Toolbox::Toolbox() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6941: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 24 bytes in 1 blocks are possibly lost in loss record 88 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x492DBE5: Gdk::Screen_Class::wrap_new(_GObject*) (in /usr/lib/libgdkmm-2.4.so.1.0.30)&lt;br /&gt;
==9312==    by 0x4D5C252: (within /usr/lib/libglibmm-2.4.so.1.0.24)&lt;br /&gt;
==9312==    by 0x4D5C304: Glib::wrap_auto(_GObject*, bool) (in /usr/lib/libglibmm-2.4.so.1.0.24)&lt;br /&gt;
==9312==    by 0x492DDDC: Glib::wrap(_GdkScreen*, bool) (in /usr/lib/libgdkmm-2.4.so.1.0.30)&lt;br /&gt;
==9312==    by 0x4825EA4: Gtk::Widget_Class::screen_changed_callback(_GtkWidget*, _GdkScreen*) (in /usr/lib/libgtkmm-&lt;br /&gt;
2.4.so.1.0.30)&lt;br /&gt;
==9312==    by 0x5047EE8: g_cclosure_marshal_VOID__OBJECT (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9312==    by 0x5039E48: (within /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9312==    by 0x503B62A: g_closure_invoke (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9312==    by 0x504C752: (within /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9312==    by 0x504D626: g_signal_emit_valist (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9312==    by 0x504D7E8: g_signal_emit (in /usr/lib/libgobject-2.0.so.0.1200.11)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 95 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E6781: studio::LayerTree::create_param_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBEE: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 96 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81BAC74: TimeTrackView::TimeTrackView() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81B8B3C: studio::Dock_Timetrack::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /&lt;br /&gt;
usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 98 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E6BBB: studio::LayerTree::create_param_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBEE: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 99 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E667A: studio::LayerTree::create_param_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBEE: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 100 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E6612: studio::LayerTree::create_param_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBEE: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 101 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E65E6: studio::LayerTree::create_param_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBEE: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 102 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82EFA4D: Gtk::CellRenderer* Gtk::CellRenderer_Generation::generate_cellrenderer&amp;lt;float&amp;gt;(bool) (in /us&lt;br /&gt;
r/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82E5714: studio::LayerTree::create_layer_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBE6: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 104 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E543F: studio::LayerTree::create_layer_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBE6: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 105 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E546F: studio::LayerTree::create_layer_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBE6: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 106 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E52E1: studio::LayerTree::create_layer_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBE6: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 107 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81B1723: studio::Dock_MetaData::Dock_MetaData() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6D27: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 108 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81B15FF: studio::Dock_MetaData::Dock_MetaData() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6D27: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 109 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E6B8F: studio::LayerTree::create_param_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBEE: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 110 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81BAB31: TimeTrackView::TimeTrackView() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81B8B3C: studio::Dock_Timetrack::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /&lt;br /&gt;
usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 112 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82DF591: studio::KeyframeTree::KeyframeTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A70FF: studio::Dock_Keyframes::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /&lt;br /&gt;
usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 113 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82DF473: studio::KeyframeTree::KeyframeTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A70FF: studio::Dock_Keyframes::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /&lt;br /&gt;
usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 114 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82DF447: studio::KeyframeTree::KeyframeTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A70FF: studio::Dock_Keyframes::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /&lt;br /&gt;
usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 115 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82DF28C: studio::KeyframeTree::KeyframeTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A70FF: studio::Dock_Keyframes::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /&lt;br /&gt;
usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 117 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82DF0BF: studio::KeyframeTree::KeyframeTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A70FF: studio::Dock_Keyframes::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /&lt;br /&gt;
usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 119 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81982A7: studio::Dock_Canvases::create_canvas_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x8198A44: studio::Dock_Canvases::Dock_Canvases() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6B23: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 120 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x47D120A: Gtk::HScale::HScale(double, double, double) (in /usr/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9312==    by 0x83B2B64: studio::Widget_Defaults::Widget_Defaults() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82B3B47: studio::Toolbox::Toolbox() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6941: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 121 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E5113: studio::LayerTree::create_layer_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBE6: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 122 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E5143: studio::LayerTree::create_layer_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBE6: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 123 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82DA787: studio::ChildrenTree::ChildrenTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819BD1F: studio::Dock_Children::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /u&lt;br /&gt;
sr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 124 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82DA4EF: studio::ChildrenTree::ChildrenTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819BD1F: studio::Dock_Children::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /u&lt;br /&gt;
sr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 126 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E2165: studio::LayerGroupTree::LayerGroupTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A8E25: studio::Dock_LayerGroups::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in&lt;br /&gt;
 /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 127 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x4800EF5: Gtk::Tooltips_Class::wrap_new(_GObject*) (in /usr/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9312==    by 0x4D5C252: (within /usr/lib/libglibmm-2.4.so.1.0.24)&lt;br /&gt;
==9312==    by 0x4D5C304: Glib::wrap_auto(_GObject*, bool) (in /usr/lib/libglibmm-2.4.so.1.0.24)&lt;br /&gt;
==9312==    by 0x4801194: Glib::wrap(_GtkTooltips*, bool) (in /usr/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9312==    by 0x47FD4A0: Gtk::Toolbar::get_tooltips_object() const (in /usr/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9312==    by 0x81BE2E0: studio::Dockable::add_button(Gtk::StockID const&amp;amp;, std::string const&amp;amp;) (in /usr/local/bin/sy&lt;br /&gt;
nfigstudio)&lt;br /&gt;
==9312==    by 0x81B19A6: studio::Dock_MetaData::Dock_MetaData() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6D27: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 128 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81A04E7: studio::Dock_History::create_action_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A2E14: studio::Dock_History::Dock_History() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6AA2: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 129 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81A0517: studio::Dock_History::create_action_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A2E14: studio::Dock_History::Dock_History() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6AA2: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 130 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x483619B: Gtk::CellRenderer* Gtk::CellRenderer_Generation::generate_cellrenderer&amp;lt;bool&amp;gt;(bool) (in /usr&lt;br /&gt;
/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9312==    by 0x82E3BB9: int Gtk::TreeView::append_column_editable&amp;lt;bool&amp;gt;(Glib::ustring const&amp;amp;, Gtk::TreeModelColumn&amp;lt;&lt;br /&gt;
bool&amp;gt; const&amp;amp;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82E2136: studio::LayerGroupTree::LayerGroupTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A8E25: studio::Dock_LayerGroups::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in&lt;br /&gt;
 /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 131 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81A030F: studio::Dock_History::create_action_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A2E14: studio::Dock_History::Dock_History() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6AA2: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 132 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E6908: studio::LayerTree::create_param_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBEE: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 133 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81A033B: studio::Dock_History::create_action_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A2E14: studio::Dock_History::Dock_History() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6AA2: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 134 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E3B24: int Gtk::TreeView::append_column_editable&amp;lt;bool&amp;gt;(Glib::ustring const&amp;amp;, Gtk::TreeModelColumn&amp;lt;&lt;br /&gt;
bool&amp;gt; const&amp;amp;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82E2136: studio::LayerGroupTree::LayerGroupTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A8E25: studio::Dock_LayerGroups::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in&lt;br /&gt;
 /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 135 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81A0673: studio::Dock_History::create_action_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A2E14: studio::Dock_History::Dock_History() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6AA2: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 136 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81A0643: studio::Dock_History::create_action_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A2E14: studio::Dock_History::Dock_History() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6AA2: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 137 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82DA60D: studio::ChildrenTree::ChildrenTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819BD1F: studio::Dock_Children::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /u&lt;br /&gt;
sr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 28 bytes in 1 blocks are possibly lost in loss record 138 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82DA4C3: studio::ChildrenTree::ChildrenTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819BD1F: studio::Dock_Children::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /u&lt;br /&gt;
sr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 32 bytes in 1 blocks are possibly lost in loss record 142 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82EBFB3: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 32 bytes in 1 blocks are possibly lost in loss record 145 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82EBEB2: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 32 bytes in 1 blocks are possibly lost in loss record 147 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x83F8CC2: studio::Dialog_Setup::Dialog_Setup() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7592: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 32 bytes in 1 blocks are possibly lost in loss record 148 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x83EA209: studio::Dialog_Gradient::Dialog_Gradient() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E711E: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 32 bytes in 1 blocks are possibly lost in loss record 150 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E5AAF: studio::LayerTree::create_layer_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBE6: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 32 bytes in 1 blocks are possibly lost in loss record 151 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81A5275: studio::Dock_Info::Dock_Info() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6E29: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 32 bytes in 1 blocks are possibly lost in loss record 152 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81A4EF0: studio::Dock_Info::Dock_Info() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6E29: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 32 bytes in 1 blocks are possibly lost in loss record 153 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81A4CB6: studio::Dock_Info::Dock_Info() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6E29: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 32 bytes in 1 blocks are possibly lost in loss record 154 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82DAC14: studio::ChildrenTree::ChildrenTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819BD1F: studio::Dock_Children::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /u&lt;br /&gt;
sr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 32 bytes in 1 blocks are possibly lost in loss record 157 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81A4F89: studio::Dock_Info::Dock_Info() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6E29: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 32 bytes in 1 blocks are possibly lost in loss record 158 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x81B1859: studio::Dock_MetaData::Dock_MetaData() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E6D27: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 32 bytes in 1 blocks are possibly lost in loss record 159 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x82E70A7: studio::LayerTree::create_param_tree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82EBBEE: studio::LayerTree::LayerTree() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81A9BA9: studio::Dock_Layers::init_canvas_view_vfunc(etl::loose_handle&amp;lt;studio::CanvasView&amp;gt;) (in /usr&lt;br /&gt;
/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x819AFED: studio::Dock_CanvasSpecific::init_canvas_view(studio::CanvasView*) (in /usr/local/bin/synfi&lt;br /&gt;
gstudio)&lt;br /&gt;
==9312==    by 0x82342C6: studio::CanvasView::create(etl::loose_handle&amp;lt;studio::Instance&amp;gt;, etl::handle&amp;lt;synfig::Canvas&amp;gt;&lt;br /&gt;
) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827409F: studio::Instance::find_canvas_view(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigst&lt;br /&gt;
udio)&lt;br /&gt;
==9312==    by 0x8278D9A: studio::Instance::focus(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x827BF4D: studio::Instance::create(etl::handle&amp;lt;synfig::Canvas&amp;gt;) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81D1BCC: studio::App::new_instance() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81E7E63: studio::App::App(int*, char***) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x81C9D70: main (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==&lt;br /&gt;
==9312==&lt;br /&gt;
==9312== 32 bytes in 1 blocks are possibly lost in loss record 160 of 1,058&lt;br /&gt;
==9312==    at 0x4020DC5: operator new(unsigned) (vg_replace_malloc.c:163)&lt;br /&gt;
==9312==    by 0x47FCB45: Gtk::Toolbar_Class::wrap_new(_GObject*) (in /usr/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9312==    by 0x4D5C252: (within /usr/lib/libglibmm-2.4.so.1.0.24)&lt;br /&gt;
==9312==    by 0x4D5C304: Glib::wrap_auto(_GObject*, bool) (in /usr/lib/libglibmm-2.4.so.1.0.24)&lt;br /&gt;
==9312==    by 0x481D4B4: Glib::wrap(_GtkWidget*, bool) (in /usr/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9312==    by 0x4818BA9: Gtk::UIManager::get_widget(Glib::ustring const&amp;amp;) (in /usr/lib/libgtkmm-2.4.so.1.0.30)&lt;br /&gt;
==9312==    by 0x838283B: studio::StateSketch_Context::refresh_tool_options() (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x838503A: studio::StateSketch_Context::StateSketch_Context(studio::CanvasView*) (in /usr/local/bin/sy&lt;br /&gt;
nfigstudio)&lt;br /&gt;
==9312==    by 0x8388258: etl::smach&amp;lt;studio::CanvasView, studio::EventKey, etl::mutex_null&amp;gt;::state&amp;lt;studio::StateSketc&lt;br /&gt;
h_Context&amp;gt;::enter_state(studio::CanvasView*) const (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82A9668: studio::Toolbox::change_state_(etl::smach&amp;lt;studio::CanvasView, studio::EventKey, etl::mutex_&lt;br /&gt;
null&amp;gt;::state_base const*) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x82B6B08: sigc::internal::slot_call0&amp;lt;sigc::bind_functor&amp;lt;-1, sigc::bound_mem_functor1&amp;lt;void, studio::To&lt;br /&gt;
olbox, etl::smach&amp;lt;studio::CanvasView, studio::EventKey, etl::mutex_null&amp;gt;::state_base const*&amp;gt;, etl::smach&amp;lt;studio::Canv&lt;br /&gt;
asView, studio::EventKey, etl::mutex_null&amp;gt;::state_base const*, sigc::nil, etl::smach&amp;lt;studio::CanvasView, studio::Even&lt;br /&gt;
tKey, etl::mutex_null&amp;gt;::state_base const*, etl::smach&amp;lt;studio::CanvasView, studio::EventKey, etl::mutex_null&amp;gt;::state_b&lt;br /&gt;
ase const*, etl::smach&amp;lt;studio::CanvasView, studio::EventKey, etl::mutex_null&amp;gt;::state_base const*, etl::smach&amp;lt;studio::&lt;br /&gt;
CanvasView, studio::EventKey, etl::mutex_null&amp;gt;::state_base const*, etl::smach&amp;lt;studio::CanvasView, studio::EventKey, e&lt;br /&gt;
tl::mutex_null&amp;gt;::state_base const*&amp;gt;, void&amp;gt;::call_it(sigc::internal::slot_rep*) (in /usr/local/bin/synfigstudio)&lt;br /&gt;
==9312==    by 0x4D55339: Glib::SignalProxyNormal::slot0_void_callback(_GObject*, void*) (in /usr/lib/libglibmm-2.4.s&lt;br /&gt;
o.1.0.24)&lt;br /&gt;
==9312==&lt;br /&gt;
&lt;br /&gt;
[/code]&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Doc:Gimp2synfig&amp;diff=6980</id>
		<title>Doc:Gimp2synfig</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Doc:Gimp2synfig&amp;diff=6980"/>
				<updated>2008-04-26T21:28:34Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: typos&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To simplify the work of animating my cartoon about a mouse, a plug-in for the [http://gimp.org/ GIMP] raster editor has been written, to allow the direct exporting of multi-layered images to corresponding layers of the 2D animation package Synfig.&lt;br /&gt;
&lt;br /&gt;
The plug-in registers itself in the GIMP image menu &amp;lt;image&amp;gt;-&amp;gt; File-&amp;gt; Export-&amp;gt; Synfig.&lt;br /&gt;
&lt;br /&gt;
[http://img246.imageshack.us/my.php?image=gimp2synfigmenuxh9.jpg http://img246.imageshack.us/img246/4126/gimp2synfigmenuxh9.th.jpg]&lt;br /&gt;
&lt;br /&gt;
There are export options you can choose. If the field &amp;quot;output path&amp;quot; is empty, the synfig canvas will be kept in the same directory as the initial picture.&lt;br /&gt;
&lt;br /&gt;
[http://img292.imageshack.us/my.php?image=gimp2synfigsettingsvs3.jpg http://img292.imageshack.us/img292/269/gimp2synfigsettingsvs3.th.jpg]&lt;br /&gt;
&lt;br /&gt;
Here is the result:&lt;br /&gt;
&lt;br /&gt;
[http://img201.imageshack.us/my.php?image=gimp2synfig003yn6.jpg http://img201.imageshack.us/img201/9369/gimp2synfig003yn6.th.jpg]&lt;br /&gt;
&lt;br /&gt;
On the left you can see the initial image in Gimp, and on the right the same image imported into Synfig.  &lt;br /&gt;
&lt;br /&gt;
After adding a scale layer, the images cannot be distinguished.&lt;br /&gt;
&lt;br /&gt;
[http://img151.imageshack.us/my.php?image=gimp2synfig003withgammafd6.jpg http://img151.imageshack.us/img151/5450/gimp2synfig003withgammafd6.th.jpg]&lt;br /&gt;
&lt;br /&gt;
You can download the [http://akhil.nm.ru/tools/pygimp/synfigexport.py GIMP2.4synfig plugin], or [http://dooglus.rincevent.net/random/synfigexport.py GIMP2.2synfig plugin].&lt;br /&gt;
&lt;br /&gt;
To make it work, gimp must support Python, and the most recent version of Python must be installed on your computer. &lt;br /&gt;
&lt;br /&gt;
To install this plug-in, simply put the file in ~/.gimp-*/plug-ins/ and make it executable (chmod +x synfigexport.py), then restart gimp.&lt;br /&gt;
&lt;br /&gt;
This program is licensed under Creative Commons Attribution 3.0 Unported License. Distribution and updating of the code is appreciated.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Dev:Contribute_to_Code&amp;diff=6979</id>
		<title>Dev:Contribute to Code</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Dev:Contribute_to_Code&amp;diff=6979"/>
				<updated>2008-04-26T21:10:42Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: typos&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Code]]&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
You should know by the [[History|history]], that this program was initially written by an animation company, [[History|Voria Studios]]. Since the code of Synfig was released under [[License|GPL licence]] and turned into an open source project, there have been made some modifications to the code, which allows you to remove bugs and to add some new functionality. &lt;br /&gt;
&lt;br /&gt;
The only documentation you can get, is the source-code itself and the automatically generated [http://synfig.org/api/ API docs] by [http://www.doxygen.org doxygen].&lt;br /&gt;
This page tries to collect all the knowledge acquired by the current developers and to create typical guides for common tasks which would allow you to add new features and make the program grow. &lt;br /&gt;
&lt;br /&gt;
Feel free to add here all the information you can get from the experience of reading and modifying the source code or simply add your request to get more details from coders more familiar with the source. Hopefully they will be able to tell you, how it works and where to dive in.&lt;br /&gt;
&lt;br /&gt;
== Common tasks ==&lt;br /&gt;
&lt;br /&gt;
* [[Source:Adding a Layer|Adding Layers to Synfig]]: this guide aids you to understand, how the layers work and how to add a new layer type.&lt;br /&gt;
* [[Source:Adding a Panel-Part I| Adding Panels to Synfigstudio]]: This guide explains, how to add a new panel and the objects on it.&lt;br /&gt;
&lt;br /&gt;
== Things you want to know about the code ==&lt;br /&gt;
&lt;br /&gt;
* Please add here a brief description of the things you want to know about the code and how to accomplish some task. Someone else will surely know it, and can help you to start developing on synfig.&lt;br /&gt;
&lt;br /&gt;
* Is there anywhere any kind of overview? Any sort of brief description of what each program does/is? Is synfigstudio the GUI for synfig? What's the ETL?&lt;br /&gt;
&lt;br /&gt;
==Documenting the code ==&lt;br /&gt;
&lt;br /&gt;
It would be a good thing, if all the code documentation and what is being discovered were confirmed and inserted directly in the source code itself. This would allow [http://www.doxygen.org doxygen] to generate the [http://synfig.org/api/ API docs] easily. &lt;br /&gt;
&lt;br /&gt;
Please follow these [http://www.stack.nl/~dimitri/doxygen/docblocks.html doxygen rules] to add documentation to the source code.&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	<entry>
		<id>https://www.wiki.synfig.org/index.php?title=Doc_talk:Gimp2synfig&amp;diff=6973</id>
		<title>Doc talk:Gimp2synfig</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.synfig.org/index.php?title=Doc_talk:Gimp2synfig&amp;diff=6973"/>
				<updated>2008-04-26T15:09:12Z</updated>
		
		<summary type="html">&lt;p&gt;SvH: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;vonhalenbach on IRC was using GIMP 2.2 and Python 2.5.1 and found that his generated sif output was ending after 20 lines:&lt;br /&gt;
&lt;br /&gt;
 19    &amp;lt;param name=&amp;quot;canvas&amp;quot;&amp;gt;&lt;br /&gt;
 20      &amp;lt;canvas xres=&amp;quot;10.000000&amp;quot; yres=&amp;quot;10.000000&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
whereas for me (with Python 2.5.2 and Gimp 2.4.5) it continues:&lt;br /&gt;
&lt;br /&gt;
 19    &amp;lt;param name=&amp;quot;canvas&amp;quot;&amp;gt;&lt;br /&gt;
 20      &amp;lt;canvas xres=&amp;quot;10.000000&amp;quot; yres=&amp;quot;10.000000&amp;quot;&amp;gt;&lt;br /&gt;
 21        &amp;lt;layer type=&amp;quot;import&amp;quot; active=&amp;quot;true&amp;quot; version=&amp;quot;0.1&amp;quot; desc=&amp;quot;Background.png&amp;quot;&amp;gt;&lt;br /&gt;
 22          &amp;lt;param name=&amp;quot;z_depth&amp;quot;&amp;gt;&lt;br /&gt;
 23            [...]&lt;/div&gt;</summary>
		<author><name>SvH</name></author>	</entry>

	</feed>