>
> >The slave applet is always one step behind the master applet. This is
> >very obvious after zoom changes with the mouse scroll wheel. It is
> >less obvious with rotations because of the very small difference, but
> >the difference is still there.
> >
> >
> >
> There should be a slight delay, provided the slave makes it up to the
> master applet after each move.
> But the problem with the zoom is that there's a bug that doesn't pass
> that change on.
> So that's not a major problem. Just a minor bug.
>
>
In addition to fixing this bug (which may be a minor bug, but is obvious
enough that I can't subject my users to it), I have one other
recommendation.

The javascript 'onmouseover' event is notoriously flaky.  Can the applet
actually look for mouse-driven orientation changes, then apply those changes
to a list of 'slave' applets?  The API would be as simple as

_jmolGetApplet("A").setSlave(slaveAppletName)
_jmolGetApplet("A").removeSlave(slaveAppletName)

Because the 'slave' synchronization would only trigger on actual
mouse-events, dual-syncing should work fine.

_jmolGetApplet("A").setSlave("B")
_jmolGetApplet("B").setSlave("A")

_jason
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users

Reply via email to