Re: [Jmol-users] Surprising callback behavior--object not string

[Miguel <mi...@jm...>]

Bob wrote:

> The following fixes the problem:
>
> function showmsg(n,what)=7B
>   var swhat=3Dwhat+=22=22

=5Bsnip=5D

> The only change here is the explicit conversion
> of the input parameter =22what=22 to a string.

Tim Driscoll encountered this problem with Safari back in the spring. He
came up with the same workaround ... explicitly force it to be a
JavaScript string.

> Apparently the callback mechanism returns a pointer
> to the java object =22what=22.

Correct.

But it is quite clear to me that this is an Apple/Safari/LiveConnect bug.=


I am calling with a java.lang.String .. and the rules for 'marshalling'
objects between JavaScript and Java are quite clear.

Whatever object type they have left it, it is not a first-class JavaScrip=
t
string.


Miguel