Bugs item #3405011, was opened at 2011-09-06 07:44 Message generated for change (Comment added) made by genete You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=757416&aid=3405011&group_id=144022
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Render Artifact Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: David Rylander (rylleman) Assigned to: Genete (genete) Summary: Active points set to off with no indication of this. Initial Comment: I've come across situations where active point for vertices is set to off but there are no visual indication of the active point status. In the attached synfig file vertex001 is set to off from document start but there are absolutely no way of knowing this frrm within Synfig itself. ---------------------------------------------------------------------- >Comment By: Genete (genete) Date: 2012-02-13 05:20 Message: OK, can load the file. The proposed solution produces other problems, like don't have one initial Off point when inserting an item smart. When an item is inserted it should be off by default if done in animation mode so then the keyframes that might exists, can keep it off when it is turned on during its creation. One possible solution maybe don't make it Off at start of time but at the creation time where it will be later turned into on, when inserted. ---------------------------------------------------------------------- Comment By: Genete (genete) Date: 2012-02-12 05:39 Message: I've reopened the bug because applying the proposed solution breaks the on/off logic. Rylleman, can you upload the sample file again?. Looks to be corrupted. ---------------------------------------------------------------------- Comment By: Genete (genete) Date: 2011-09-16 08:45 Message: This bug was caused because it is coded that when user adds a new blinepoint in animation mode, there is created a 'off' point at start of times (time.begin()). This produced some weird results when the bline is calculated: The real 'on' time of the blinepoint is not exactly the time of the 'on active point but a bit earlier. It is due to that the code uses a very small number to check if the amount of the point (the number that governs the on/off status) is very close to one. For normal cases (off time and on time normal numbers) it works fine but when the off time is time.begin() (a time earlier than any other time) the calculation gives those weird results. Commenting the code that inserts that artificial 'off' active point solves the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=757416&aid=3405011&group_id=144022 ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Synfig-devl mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synfig-devl
