From: Robert H. <ha...@st...> - 2008-11-26 19:36:39
|
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 out-of-memory error, I don't know. Bob On Wed, Nov 26, 2008 at 1:22 PM, Robert Hanson <ha...@st...> 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. > > -- jmolGetPropertyAsString("errorMessage") returns the error message > or "null" if there was none. > > Still could be some problems here, but I'm betting this goes a long > way to solving the problem. > > Bob > > >>> How can the interface distinguish between a script error and freezing? > > There should be no more freezing, though I don't guarantee that. > >>> >>> The interface could try to analyze the message callback stream to detect >>> script errors. But since the complexity of the messages was increased >>> during the last years it will be rather insecure and will also slow down >>> the interface. > > I'm not convinced it does slow down the interface. The message > callback stream is a dependable way to do this. All scripting errors > contain the characters "ERROR" and can be read using messageCallback > or scriptCallback > > >>> >>> So I would like to propose to implement a kind of error trapping system. >>> A possible approach would be that Jmol would look for a specific >>> function when a script error would occur. If this function would be >>> defined it would run the commands within this function. > > Not sure I understand this idea. > >>> >>> Q: What do you think about this idea? > > See how it works for you now -- again, I recommend using > scriptCallback and just checking for ERROR > > > >>> >>> 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-developers mailing list >>> Jmo...@li... >>> https://lists.sourceforge.net/lists/listinfo/jmol-developers >>> >> >> >> >> -- >> Robert M. Hanson >> Professor of Chemistry >> St. Olaf College >> 1520 St. Olaf Ave. >> Northfield, MN 55057 >> http://www.stolaf.edu/people/hansonr >> phone: 507-786-3107 >> >> >> If nature does not answer first what we want, >> it is better to take what answer we get. >> >> -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 >> > > > > -- > Robert M. Hanson > Professor of Chemistry > St. Olaf College > 1520 St. Olaf Ave. > Northfield, MN 55057 > http://www.stolaf.edu/people/hansonr > phone: 507-786-3107 > > > If nature does not answer first what we want, > it is better to take what answer we get. > > -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 > -- Robert M. Hanson Professor of Chemistry St. Olaf College 1520 St. Olaf Ave. Northfield, MN 55057 http://www.stolaf.edu/people/hansonr phone: 507-786-3107 If nature does not answer first what we want, it is better to take what answer we get. -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 |