From: Otis R. <osr...@ch...> - 2012-06-22 02:45:00
|
Rolf, I didn't even have Java debugging turned on. I thought it was on by default. I have it on now. Thanks for the suggestion. Otis -- Otis Rothenberger ot...@ch... http://chemagic.com On Jun 21, 2012, at 11:24 AM, Rolf Huehne wrote: > On 06/21/2012 03:43 PM, Otis Rothenberger wrote: >> When I "play" with our Jmol model kit application for a period of time, I will sometimes encounter what I'll call applet fatigue. The page does not lock, nor am I prevented from using mouse model manipulation, but I cannot issue jmolScript commands. >> >> My gut feel is that this is not a Jmol problem. Things that cause this fatigue have worked numerous times prior to the onset of a fatigue incident. I cannot raise the Jmol console to look at history, however. >> >> Does this sound like a Java memory issue? Does anyone else have experience with "applet fatigue?" >> > I probably observed this kind of behaviour sometimes after java errors. > Usually Jmol totally freezed but with some errors only the scripting > engine seemed to be blocked but Jmol still reacted to some mouse actions. > > Do you see any error messages in the Java console if "applet fatigue" > occurs? > > Regards, > Rolf > > ------------------------------------------------------------------------------ > 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 > Jmo...@li... > https://lists.sourceforge.net/lists/listinfo/jmol-users |