> > > > In the following page by Eric Martz, you can see how this works in > > > > Chime. > > > > > > > http://www.umass.edu/microbio/chime/chimehow/fs_cmdln.htm > > > > > IIRC, if you send a long script to Chime, the messages returning are > scrambled > > (IOW, not in the same order as they went to Chime). I don't recall the > > details, and maybe this has no bearing on JMol - maybe Paul can say more? > > > > Of course Tim ! (even if I don't understand what IIRC means...) > > The scrambling issue comes with Chime and *Netscape 4.X* > It's a problem between the plug-in and the browser, independant from Chime. > For long scripts, messages returned to a javascript function via the > MessageCallback method, come back in a wrong order. > Eric Martz gives examples these idiosynchrasies here > http://molvis.sdsc.edu/shared/scrambld.txt, and a complete description of > this behaviour there : http://molvis.sdsc.edu/shared/unscramb.txt > This problem doesn't occur with IE, nor with mozilla. So it's only > Chime-Communicator specific. > > To solve it, Chime developpers add a third argument to the messagecallback > method, wich is the number of the message. That is to say, with Chime, the > function called by messagecallback gets these parameters : > - 1st : the plugin name > - 2nd : the message itself > - 3rd : the message's number as it is adressed by Chime > > Some applications using Chime implement functions to reorder the messages, > using this third parameter. > > I think that it's not usefull in Jmol as long as this communication issue > doesn't exist... > > Paul >
------------------------------------------------------- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl _______________________________________________ Jmol-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-users
