Thanks, Bob. I'm rather puzzled I think that all has started when I changed from having Jmol files below the page folder to having them on a sister folder. The script files are always with Jmol or below it. So it's the position relative to the html that makes the difference.
Comparing to the app will not give much info, since from console it works. It's just the button. > Very odd that the system can't find it. This could be an odd > threading issue -- the thread that runs from a click of a button is > not the same thread that runs when you use the Jmol console or menu. Must be that. Any chance to sort it out or an alternative? I wanted to keep a single copy of Jmol for several pages in several folders. I may resort in the end to my usual system, having Jmol at the top. But it is disconcerting that the old "models and scripts below Jmol" rule is not enough. > Local files -- sounds like a Java bug. But I could be doing something > slightly wrong there. The local script files also load properly from the console, as long as I respect the old rule. That is, right after the security error is displayed in the Java console, I can open the applet's script console, press the up key and repeat the command, it works fine. SO it's not a classical path problem. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
