Robert Hanson wrote: > Rolf, what sort of error message parsing are you trying to do that the > translation is messing up? I've just checked in bug fixes that allow > the script error messages to be translated to the new language when > the language is changed. So now in principle we could also allow for > an English-only version of any script message to be created and sent > to the errorCallback function. > As a starting point I would like to detect out-of-memory, structure load and script load errors. Within the load errors I would like to distinguish between different reasons (e.g.: not found, security problem, unknown format).
And it is also important to be able to find out which interface command provoked the error, especially for the out-of-memory errors. 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
