On Wed, Aug 25, 2010 at 2:55 PM, Eric Martz <ema...@microbio.umass.edu>wrote:
> Dear Bob,
>
> 1. Your proposal (below) sounds fine to me. I agree that I don't see
> why exit should stop e.g. spinning. That is counterintuitive to me.
> (I used exit because soon after JTAT is loaded, there is a long
> running script that fades in and fades out an echo -- I didn't want a
> spin toggle to have to wait until after that is completed.)
>
>
good -- that's added to Jmol 12.0.9
> As I understand your proposal, exit will no longer stop spinning, and
> therefore the problem I encountered will disappear.
>
> right
> 2. I missed the new feature to precede a command with "!". Where is
> that in the documentation? I expected to find it under [Jmol command
> syntax] but it is not there (should be, I think).
>
> It might be good to have #, ! (others?) listed as "commands" with
> their own sections in the documentation. I know that # is under
> comment, but a cross-ref # could link to comment.
>
> hmm. sorry
> 3. If !show spin causes that command to be executed IMMEDIATELY, IN
> THE MIDDLE of an already-running script, enabling the already running
> script to resume after "show spin", that is EXACTLY what I need,
> instead of exit (which was a kludge).
>
>
that's what it does -- insinuates itself into a running script at the next
available slot, then continues with the already running script.
> 4. In other situations, I have indeed used _spinning with Jmol script
> conditionals to toggle spinning. However, in this case, there can be
> up to 4 Jmols, and I want them all to spin, or all to not spin, not a
> mixture. So I am polling just the first Jmol and then sending
> explicit spin commands to all the others so they stay in the same
> mode. I'm sure I could have done that in other ways, including with
> the use of _spinning. However, I have working code, so I don't see
> any need to change it unless Jmol becomes incompatible with it, which
> apparently is not anticipated in this instance.
>
>
you can send messages to all applets at once with the sync command if you
want to. That works great.
> 5. I suspect it makes the most sense to have "exit" NOT clear running
> setTimeouts, so one can exit executing scripts except for
> setTimeouts. Then of course, "!exit" could clear setTimeouts as well.
>
>
I have to think about that. Maybe. But "clear all scripts" sounds to me to
be the fundamental meaning of "exit", and that would imply even timeouts.
Maybe for !exit...
Bob
--
Robert M. Hanson
Professor of Chemistry
St. Olaf College
1520 St. Olaf Ave.
Northfield, MN 55057
http://www.stolaf.edu/people/hansonr
phone: 507-786-3107
If nature does not answer first what we want,
it is better to take what answer we get.
-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
