[ka-Map-users] Problem in IE
Krassovski, Mikhail B.
krassovskimb at ornl.gov
Thu Mar 16 12:42:13 EST 2006
Thank you for you advice!
I changed the order of function calls and it works fine now.
It looks like it is the only one way for now: to keep mySetMap() the
very last one to execute. This is what comment says:
kaMap.selectMap( name )
select one of the maps that kaMap knows about and re-initialize kaMap
this new map. This function returns true if name is valid and false if
the map is invalid. Note that a return of true does not imply that the
map is fully active. You must register for the KAMAP_MAP_INITIALIZED
event since the map initialization happens asynchronously.
As I understand it means that it still does something after true is
returned and that "something" prevents next code running. It is strange
than it stumbles only in IE.
Thank you very much!
> -----Original Message-----
> From: Ed Cooley [mailto:ecooley at strategysystems.com]
> Sent: Wednesday, March 15, 2006 4:52 PM
> To: Krassovski, Mikhail B.; ka-map-users at lists.maptools.org
> Subject: RE: [ka-Map-users] Problem in IE
> We had a similar problem.
> The solution we found was to not do anything until KAMAP_INITIALIZED
> myKaMap.registerForEvent( KAMAP_INITIALIZED, null, myInitialized );
> We don't start doing anything until myInitialized function is called.
> Ed Cooley
> Strategy Systems, Inc.
> 479-271-7400 - Fax: 271-7401
> From: ka-map-users-bounces at lists.maptools.org
> [mailto:ka-map-users-bounces at lists.maptools.org] On Behalf Of
> Mikhail B.
> Sent: Wednesday, March 15, 2006 1:15 PM
> To: ka-map-users at lists.maptools.org
> Subject: [ka-Map-users] Problem in IE
> First of all I would like to say 'Thank you!' for all who put his/her
> developing such a great product!
> I had no problems to set it up and customize to my needs, great job,
> you again!
> I did the whole work in Firefox (v. 220.127.116.11), but when I checked it in
> (v.6.0.2900), I found the following problem.
> I have four maps, in general they are identical, but have different
> right after map change is requested, and it works fine in Firefox, but
> in IE. The map is changed according to request, but next function is
> executed and the whole thing stops. I started to check what is going
> found that process stops when mySetMap(...) is called, and problem is
> my function after it. Further tracing shows the following flow of
> (please, correct me if I'm wrong): mySetMap(...) ->
> kaMap.prototype.selectMap -> this.zoomToExtents(....) ->
> this.triggerEvent(KAMAP_EXTENTS_CHANGED, this.getGeoExtents) ->
> kaMap.prototype.getGeoExtents . It looks like the last function
> getGeoExtents return values (return [minx, miny, maxx, maxy];), but
> everything stops. I can't understand why it does that and how to fix
> you have any suggestions, I'll be very grateful!
> Misha Krassovski
> Ph. (865) 241-1859
> F.(865) 574-2232
> Carbon Dioxide Information Analysis Center
> Oak Ridge National Laboratory
> P.O. Box 2008
> Building 1509, MS 6335
> Oak Ridge, Tennessee 37831-6335
More information about the ka-Map-users