Hi Miguel,
Do you want me to first start looking into the 'Start Vibration' 'Next Vibration' menu items, by adding those as new actions, or do you think it would be better to have them as script commands, e.g.,
vibration next
vibration prev
similar to what is in the Jmol Help for the 'animate' command?
I'll hold off on that till I hear back from you, or hold off at all if you don't think we should focus on that right now. Meanwhile I try to get that hierarchy stuff to work in my AtomSetChooser/GaussianReader (when I am not forced to do my real job :-)
By the way I don't think the animate command works the way the helps describes it. It seems to be the 'frame' command itself that does what 'animate' used to do, and 'anim' seems to turn on the animation... (similar to vibration turning on the vibrations, so why no have it called animation).
I started playing with the frame commands, and it looks like to goes outside of the range of frames, which causes all the frames to be drawn at the same time, e.g., load the g98.out and do a 'frame o' (with vibration on: pretty neat, but not sure whether that was planned). Do a 'frame 1' and then a 'frame nextwrap'. Just thought I'd let you know (as if you didn't have enough things going on already :-).
Ren�
On Nov 4, 2004, at 8:36 AM, Miguel wrote:
Rene,
I just added the following methods:
boolean JmolViewer.modelSetHasVibrationVectors()
boolean JmolViewer.modelHasVibrationVectors(int modelIndex)
Miguel
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88&alloc_id065&op=click _______________________________________________ Jmol-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-developers
