Re: [Jmol-users] Problem replacing v14 with v16

[Angel H. <ang...@ua...>]

Hi Jochen
Make sure it is  not a browser cache problem. It happens when you change JSmol version in a frequently used page



 Dr. Angel Herráez
 Biochemistry and Molecular Biology,
 Dept. of Systems Biology, University of Alcalá
 E-28805 Alcalá de Henares  (Madrid), Spain
________________________________
De: Jochen Junker <joc...@fi...>
Enviado: domingo, 1 de junio de 2025 1:32
Para: jmo...@li... <jmo...@li...>
Asunto: [Jmol-users] Problem replacing v14 with v16

ATENCIÓN: Este correo electrónico se envió desde fuera de la UAH. No haga clic en enlaces ni abra archivos adjuntos a menos que reconozca al remitente y sepa que el contenido es seguro.

Hi Robert!

The update from v14 to v16 did not work as drop in for me. I have several instances of Jmol running on one page, and the first one that I create does not run properly, it is stuck at the spinner page. This is the console output:

loadScript /jsmol/j2s/core/package.js
loadScript /jsmol/j2s/core/corejmol.z.js
loadScript /jsmol/j2s/J/translation/PO.js
loadScript /jsmol/j2s/core/corescript.z.js
JSmol exec jmolc start applet null
Jmol JavaScript applet jmolc__8156526783576168__ initializing
Jmol getValue debug null
Jmol getValue logLevel null
Jmol getValue allowjavascript true
AppletRegistry.checkIn(jmolc__8156526783576168__)
IndexSizeError: Index or size is negative or greater than the allowed amount

All instances that are created afterwards work fine.
Just changing the loading path back to v14 and everything is fine again. Instead of the error message it goes on with viewerOptions.
Can you help me with any idea what it could be? I suspected it to be a racing condition problem, and v14 was simply faster, but that does not seem to be the case.

Best Regards,
Jochen



_______________________________________________
Jmol-users mailing list
Jmo...@li...
https://lists.sourceforge.net/lists/listinfo/jmol-users