131p9, Windows, .cel, goto, upframe
Posted: 10.08.2003, 07:31
Not sure if this is a bug, or as-designed ...
Is the upframe parameter in the goto command in .cel scripting supposed to set the specified Coordinate System or merely use it for the goto?
For example:
* Select Earth (Interactively)
* Goto Earth (Interactively)
* Set Follow, Track or whatever (Interactively)
* Manually rotate the Earth in 2 directions
* Run the following script:
The script produces the following:
* The Earth is rotated in some direction
* The mode(s) you set interactively are not cleared
* The upframe value (chase) is not set as the active CoordSys
Is this what goto/upframe is supposed to be doing? Or should the new Coordinate System be Chase?
Is the upframe parameter in the goto command in .cel scripting supposed to set the specified Coordinate System or merely use it for the goto?
For example:
* Select Earth (Interactively)
* Goto Earth (Interactively)
* Set Follow, Track or whatever (Interactively)
* Manually rotate the Earth in 2 directions
* Run the following script:
Code: Select all
{
select { object "Earth" }
goto { time 3
distance 10.0
upframe "chase" }
wait { duration 3 }
}
The script produces the following:
* The Earth is rotated in some direction
* The mode(s) you set interactively are not cleared
* The upframe value (chase) is not set as the active CoordSys
Is this what goto/upframe is supposed to be doing? Or should the new Coordinate System be Chase?