Hello, sorry, now I understand, that the table is not applicable for animateMotion using a path attribute or a mpath element. This part of the problem was my error. The second can simply be avoided by removing 'control' from 'control point'. Something related: The distance definition of transform list type rotate seems to be a little bit strange (physical argumentation), because it mixes up angles and lengths. Because they have different units, calculations according to this will lead to funny effects, comparing the same animation with just a coordinate system scaled differently for lengths. It is maybe more useful to define the distances for the angle and the translation independently, using a replacement like translate(-cx,-cy) rotate(angleA) translate(cx,cy) and the distance definitions for value types angle and transform list type translate. Best wishesReceived on Tuesday, 13 June 2006 12:35:11 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:13 UTC