Ok, didn't know about it. Set the callback and using jmolScriptWait now.
Looking fine, thanks again.
Martin
On 18.06.12 16:00, Angel Herráez wrote:
>> It turns out, I was doing the load using "jmolScriptWait(...)". Using
>> "jmolScript(...)", it seems to have no problem with permissions.
> Ah! That clicks a memory
>
> This is called use of threads. I have fixed security errors by setting
> useCommandThread
> Look for that word in the online scripting doc
>
> I used it like this:
>
> jmolInitialize("..");
> jmolSetCallback("UseCommandThread","true");
> jmolApplet(550);
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Jmol-users mailing list
> Jmol-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jmol-users
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
