Robert Hanson wrote:
sorry -- pressed SEND prematurely.
Rolf, please check what I just checked in for Jmol 11.7.14. I think it
just might work for you.
-- Out of Memory errors -- Java heap space -- now caught by the
script processor and image creator.
--
As long as it is not assured that Jmol can work normally afterwards,
freezing might be better (possibly after sending an appropriate error
message).
freezing is never better. I'll look into that error message. I did
make a few changes just this morning. So take a look at that.
Note that it
Hi developers,
the increasing power of Jmol is fantastic. But if this power is used
within the applet it greatly enhances the danger of freezing Jmol by an
out of memory error.
When I started to build the JenaLib Jmol Viewer interface (now Jena3D)
about 3 years ago there was only one
Rolf, it is great that you are tackling this.
On Wed, Nov 26, 2008 at 8:02 AM, Rolf Huehne [EMAIL PROTECTED] wrote:
Hi developers,
the increasing power of Jmol is fantastic. But if this power is used
within the applet it greatly enhances the danger of freezing Jmol by an
out of memory
sorry -- pressed SEND prematurely.
Rolf, please check what I just checked in for Jmol 11.7.14. I think it
just might work for you.
-- Out of Memory errors -- Java heap space -- now caught by the
script processor and image creator.
-- jmolGetPropertyAsString(errorMessage) returns the error
Oh, it is true that translations can change the ERROR message to
something else. So perhaps jmolGetPropertyAsString(errorMessage) is
a particularly good idea. If you execute that you should be able to
tell immediately whenever an error has occurred, including out of
memory. What you do after an
