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.
Thanks very much,
Tom
On Thu, Aug 28, 2008 at 11:13 AM, Angel Herráez <[EMAIL PROTECTED]>wrote:
> Hi Tom
>
> I'm probably late in joining this thread, but since there has been no final
> comment, here's
> my 2 cents
>
> 1)
> Your problem looks to me as more related to a specific browser and JVM that
> to Jmol
> version (but I may be wrong). Of course, memory is an issue.
>
> 2)
> > i) be able to stipulate the size of the popup Applet and have it be a
> fixed size, or
>
> You can always specify a fixed size applet; if the user maximizes the
> window, he will see
> blank space around the applet. (But it's great to be able to increase the
> applet size at will;
> maybe you could include a warning in yor pop-up window; after all, the
> memory allocated to
> Java is an user option.
>
> To the point:
> jmolApplet(600,"script javascript:getState()")
> will give you a fixed size, 600 pixels, square applet.
>
> 3)
> > is there a means of specifying the size of the popup window and not
> allowing it to be
> > resized once created??
>
> Certainly!
> Say you are using
>
>
> woptions="menubar=yes,resizable=1,scrollbars,alwaysRaised,width=600,height=600,left=50
> "
> newwin=open("JmolPopup.htm","jmol_"+sm,woptions)
>
> Then, change to
>
> woptions="menubar=yes,resizable=0,scrollbars,alwaysRaised,width=600,height=600,left=50
> "
>
>
> 4)
> > ii) your idea, to have an upper limit on how big it can get.
>
> I find this very tricky to implement, if even possible.
>
>
> 5)
> > Curiously, the popup window is more resistant to this blanking effect
> using MS IExplorer
> > than with Firefox (3.0.1).
>
> In my experience, Firefox (2.0) implementation of JVM (1.5 - 1.6) is much
> more unstable
> than IE's
>
>
>
>
> -------------------------------------------------------------------------
> 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
>
-------------------------------------------------------------------------
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
