Closed adambelis closed 1 day ago
Not able to replicate, please provide more info or a test project.
Ahh, that's what you mean when you said paths.
Paths like this does not support expressions etc and of course will crash, didn't think about that.
Will need to figure out a workaround or disable this function when paths are involved
yes disbling for path would make sense . or just ignore command for path+ add warning this feature is not suported
Will first check if there is a possibility to enable it for paths, but I assume expressions are disabled internally for a reason.
its probably non trivial to create such a keyframnes. since it would need to know how create new shapes by keeping track of position of every node and handle .
Yes, you are correct. The easing algorithm will always return bad values that don't "compute" with the paths (why we crash), so it's probably best to just find a way to disable this feature for paths.
i mean it would be cool feature to add in future just not that easy
I agree, but at this point we just need to avoid a crash.
Crash fixed in https://github.com/friction2d/friction/commit/de4bc1048fcc8f4bf765f4f17b0294153e8469a1
Will add support for status messages later.
Add status message in https://github.com/friction2d/friction/commit/4e824b1921f19532511c02e738fe93c8cc6fd6c6
I consider this issue fixed.
master win 10