Rolf Huehne wrote: > Thomas Stout wrote: >> Thanks Angel -- >> >> Yes, it definitely turned out to be a memory issue. My inexperience is >> another! I was stumped since the Jmol graphic stopped responding, but Jmol >> itself was still running and "doing stuff" -- I could still enter commands >> into the console and get appropriate responses. Now I know that that is a >> hallmark of Java exceptions, including out-of-memory errors. >> >> With regard to "large" windows and the memory issue, I've settled here on >> creating a pop-up window that is large enough for end-users to have a "big >> view" but which is fixed in size so that I know that it won't immediately >> eat up all of the memory. I've given up the ability for them to re-size, >> but it seems a reasonable trade-off. > > Instead of providing an automatic resize function you could provide a > manual resize option using input fields. This way you could easily set a > maximum size limit by your Javascript code that does the actual resizing. >
You wouldn't even need input fields. You could tie for example the '<body>' tag with the 'onResize' event to a Javascript function that resizes the applet with an upper limit. I just did a similar thing (with a lower limit) a few days ago for our PDB file viewer: http://www.fli-leibniz.de/cgi-bin/idb_send-rh.pl?CODE=1deh&MIME=html Regards, Rolf ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Jmol-users mailing list Jmol-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-users
