If you set up a messageCallback, then translation is supposed to be
turned off by default for all error messages. You see this message in
the Java console upon applet startup:
Note -- Presence of message callback will disable translation; to
enable message translation use jmolSetTranslation(true)
I understood that there was a mechanism (setting) to prevent error
messages from being translated. From the recent discussion, I am not
clear as whether that is not working as I thought it would.
-
This SF.Net email is spon
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 all
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 versio
this is fixed.
On Wed, Dec 3, 2008 at 9:28 AM, Rolf Huehne <[EMAIL PROTECTED]> wrote:
> Robert Hanson wrote:
>> great -- so let me know if that doesn't work for you.
>>
> It looks as if "-j" doesn't work properly (version 11.6.3 and SVN
> revision 10421).
>
> When I try to set a variable within th
Ah, Rolf notes that the app -j "script commands here" option is not
implemented correctly in Jmol 11.7.15. It will be in 11.7.16.
>>
>> To combine command-line scripts with file-based scripts, use the -j
>> flag and include in it ".;script file1.txt;script file2.txt"
>>
>> Quotes may be tricky
6 matches
Mail list logo
