Rene wrote: > To me an animation is a sequence of frames, while a vibration is the > visualization of vector information in a single frame, where I use the > term frame as the 'frame' in the scripting language, which I think is > equivalent to a Model or AtomSet. Still with me? :-)
Yes >> What is the example of wanting to animate a series of AtomSets that is >> a subset of the complete AtomSetCollection? > > If you open up the H2O_3.log in the gaussian samples and look at the > AtomSetChooser, you will see that there are 6 branches. The first > branch consists of two sets of atomsets, the Input and the Standard > orientations that were encountered for the geometry optimization. > I would like to be able to 'select' the Input orientations and only > animate those. You can't see that from the tree, but the AtomSetIndex > values for those are 0, 2, 4, 6, 8, while the Standard ones are 1, 3, > 5, 7, 9 (since each step outputs both). But, why would you want to animate these things. They are not a movie. They are completely separate snapshots. You are probably going to say that you want to see it as it changes from one state to another. But for me, that is a slide show, not an animation. I think of animations as running at 30 frames per second. It is true that the 'animation fps #' command exists, but that is for Chime compatibility and for compatibility with existing animations. I would like to interpolate frames for all of those so that they run at 30 frames per second, with the user-specified frames as 'key-frames'. I think that you want to build your slide show using existing commands. frame 1; delay .5 frame 3; delay .5 frame 5; delay .5 frame 7; delay .5 loop > I would need to modify the AtomSetChooser and add an animate button for > that, which I haven't done yet, partly because I am not very good at > the user interface and was wondering whether I should use a slider, > play, stop etc. 'buttons' like the Animate... window had in v9. >>> Question: Do you think it makes sense to have the look-and-feel of the >>> application be determined by the OS. I was surprised by how the tree >>> (and divider bar in the split pane) looks different with the >>> look-and-feel that Jmol currently has. >> >> Not sure exactly what you are saying. >> >> I think that we should use standard swing controls whenever possible. > > If you look at the AtomChooserTreeDemo.java that I sent a few days ago, > Sun uses the UIManager.setLookAndFeel. I added the snippet of code > here: At this point I have very little time to think about the Jmol application UI. 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
