Changes between Version 5 and Version 6 of AnimationCommands

Timestamp:

Jun 14, 2011, 2:39:49 PM (15 years ago)

Author:

Darren Weber

Comment:

--

AnimationCommands

@@ -2 +2 @@
 = Animation Commands =
 
-This page defines the animation command syntax and expected behavior (this is related to ticket:9055, see also ticket:9404).  
+This page defines the animation command syntax and expected behavior (this is related to ticket:9055, see also ticket:9404).  The command syntax is implemented in these [http://plato.cgl.ucsf.edu/trac/chimera/browser/trunk/libs/Animate/Commands.py animation commands].
 
 == Note on Syntax Style ==
@@ -28 +28 @@
 
 ==== Notes ====
- - "scene-name" and "trans-name" are user-specified, see (2) for the latter.
+ - "scene-name" and "trans-name" are user-specified, see (2) for the latter.  The "trans-name" is optional -- omitting it uses a "default" transition.
  - default scene not necessary.
  - save corresponds to scadd.
@@ -86 +86 @@
  - Does this limit transitions (other than positions, which would be splined as in "fly") to depending on only the bracketing pair of scenes?  Do we need fancier transitions that also depend on further preceding and following scenes?
  - How does animation integrate with recording, 2dlabels, coordset, other commands with frame arguments (move,turn,rock,roll)? Simply as interleaved commands between "movie record" and "movie stop"? Could coordset or 2dlabels changes occur at the same time as other transitions?
+
+== Scooter's revision ==
+
+Scooter's proposes two minor modifications.
+
+(1) change
+{{{
+scene scene-name (save | reset [frames[,trans-name]])
+}}}
+to only
+{{{
+scene scene-name (save | reset )
+}}}
+thus disallowing gradual transitions using the "scene" command.   Instead only the "animate" command would show gradual transitions.
+
+(2) have a special scene name that always means the current scene.  Then "animate" could be used with same syntax as in my original suggestion to go from the current scene to any other.