Login
Forgot password
Register new accountWelcome to The Bug Genie
Please fill in your username and password below, and press "Continue" to log in.If you have not already registered, please use the "Register new account" tab to do so.
Please wait ...
Synfig Issue Tracker
Please wait while updating issue type...
Could not save your changes
This issue has been changed since you started editing it
Data that has been changed is highlighted in red below. Undo your changes to see the updated information
You have changed this issue, but haven't saved your changes yet. To save it, press the Save changes button to the right
This issue is blocking the next release
 This issue has been closed with status "Closed" and resolution "RESOLVED". There are no comments
This issue has no duplicates
There are no code checkins for this issue |
||||||||||||||||||||||||||||||||||||||||||
Comments (
Attached information (
Affected items (
Related issues and tasks (
Duplicate issues (
Code checkins (
Really delete this comment?
Really delete this comment?
Really delete this comment?
I've been looking to this request and I don't find any way to solve this easily. The magic that happens when you save a composition with a non animated filename that it is converted to the relative path is due to the fact that the relative and the absolute path are stored in the layer at the time of the filename is set. That allows later to always obtain a relative path when the parameter is retrieved (you know the absolute path of the file source as well as the relative) and so, save it as relative. But when the parameter is animated, only the relative value is stored on the waypoints. With the relative values only is not possible to know what's the new path for each animated filename value because, even knowing your absolute destiny path, you don't know the absolute path for each animated filename value, so it is not possible to convert to relative when saving.
It could be possible to save as absolute when animated to eliminate that problem (when you move the document only and not the file sources) but it would create the problem of the mobility of the whole project to another location (because the paths are not relative, you have to keep the structure on any computer that want to read the document) what is a real regression in my opinion.
So I don't know how solve this bug with a simple solution.
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
retaining walls
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?