Changes between Version 10 and Version 11 of AnimationCommands

Timestamp:

Jun 22, 2011, 12:11:06 AM (15 years ago)

Author:

Darren Weber

Comment:

Realized that Scooter's proposal has significant implications for parsing "animate"

AnimationCommands

@@ -55 +55 @@
 
  2. Have a special scene name that always means the current scene.  Then "animate" could be used with the syntax of Elaine's proposal (see below) to go from the current scene to any other.
+
+'''Darren's note''':  If so, that breaks the implicit convention that the first scene in an "animate" command is always a 'snap' transition with 1 frame (as it is in [http://www.cgl.ucsf.edu/chimera/docs/UsersGuide/midas/fly.html fly]).  Also, it means that the first scene in an animate command will always use the [master-frames[,master-trans]] arguments.  It can have defaults, but not anything else, without breaking the current syntax convention and the parsing implementation for "animate".  That is, we could not specify something like:  "{{{animate 20,linear 5 scene1 scene2}}}" to get 5 linear frames to scene1 and then 20 linear frames to scene2; the extra 5 is a real headache!  (How would you parse that without making master-frames,master-trans required arguments?)