Is the FF Plug-in Broken?

[Clyde]

Hey,

I've got customer code I wrote months ago that's been working fine for
months on FF 3 and IE 7. Suddenly, within the last several days it's
no longer working on FF 3.0.1 but it's still working fine on IE7. In
fact, all of my GE code is reproducing strange results on FF 3.0.1
across every machine I've tested it on. Here's a URL with a very
simple click and fly-to example that works on IE but not on GE 3.0.1

http://www.clydeford.com/ve/ge_test.html

Any help on what's happened to cause this code not to work would be
greatly appreciated.


Clyde

[RTL]

I am having similar results. Both IE and FF apps starting misbehaving
around the time that Chrome came out.

[Roman N]

Hi Clyde,

The new API is more strict in terms of function calls and undefined
objects. I've tried your sample with Firebug installed (a debugging
tool for Firefox) and the problem is that your parameters to la.set()
in your showGE function are strings instead of floats. Try converting
the strings to floats using parseFloat():

var latitude = parseFloat(pm[n].Latitude)
...

for all parameters that should be floats. Here's a reference for the
KmlLookAt.set method:
http://code.google.com/apis/earth/documentation/reference/interface_kml_look_at.html#4bba37802619ec5b458aa7ace2ec41b9

- Roman

[Clyde]

Thanks, Roman,

Will make that conversion.

Clyde

On Sep 23, 1:25 pm, Roman N wrote:
> Hi Clyde,
>
> The new API is more strict in terms of function calls and undefined
> objects. I've tried your sample with Firebug installed (a debugging
> tool for Firefox) and the problem is that your parameters to la.set()
> in your showGE function are strings instead of floats. Try converting
> the strings to floats using parseFloat():
>
> var latitude = parseFloat(pm[n].Latitude)
> ...
>
> for all parameters that should be floats. Here's a reference for the

> KmlLookAt.set method:http://code.google.com/apis/earth/documentation/reference/interface_k...

[Gloomlord]

Roman,

Thanks... you just saved me from presumably many more hours of
headaches than I've already endured thinking about this. Thank you!

-Chris

On Sep 23, 3:25 pm, Roman N wrote:
> Hi Clyde,
>
> The new API is more strict in terms of function calls and undefined
> objects. I've tried your sample with Firebug installed (a debugging
> tool for Firefox) and the problem is that your parameters to la.set()
> in your showGE function are strings instead of floats. Try converting
> the strings to floats using parseFloat():
>
> var latitude = parseFloat(pm[n].Latitude)
> ...
>
> for all parameters that should be floats. Here's a reference for the

> KmlLookAt.set method:http://code.google.com/apis/earth/documentation/reference/interface_k...