Opened 18 years ago

Closed 17 years ago

#155 closed defect (fixed)

Initial zoom level sometimes not set

Reported by: jng Owned by:
Priority: medium Milestone:
Component: AJAX Viewer Version:
Severity: minor Keywords:
Cc: External ID: 939547

Description

Sometimes when the AJAX Viewer has finished loading, the zoom level is remains at 0 : 0.001 instead of being set to the map's initial zoom level.

Change History (7)

comment:1 by rexszeto, 18 years ago

External ID: 939547

comment:2 by ksgeograf, 17 years ago

I have noticed a similar behavior, but in my case the scalebar shows the desired zoom level, ea 1:500, but the map is clearly zoomed to 1:0.001. I have seen this in both IE and Firefox.

comment:3 by tomfukushima, 17 years ago

Hi. I had seen this a long time ago, but I haven't seen this in 1.2. Do you have steps to reproduce? Or do you notice this only in maps that have raster layers or...? Or is it platform specific?

Does disabling fastCGI and going with straight CGI fix the problem?

There might be other things to try, but that's all I've got right now.

Thanks Tom

comment:4 by ksgeograf, 17 years ago

I have seen the problem with 1.2 RC2 Win 2k3, and Enterprise 2008 win 2000. There are no raster layers in the map. There are only SDF datasources, but joined with an Access database, the map is the same for both installations.

I have not experimented with disabling FastCGI, but the problem appears to be very periodic, and I belive it to be viewer related. If I get the error, it usually repeats if I hit Ctrl+F5, but closing the browser and clearing cache will sometimes make the problem disapear. But it may just be coincidence.

comment:5 by tomfukushima, 17 years ago

In the MapGuide Users list, Nimrod Cnaan suggested the following, does this help?

you can try changing your server Data cache size to reduce round-trip loading. go to Site Administrator >> Feature Service >> Data cache size: 300.

comment:6 by jbirch, 17 years ago

Does this still happen in 2.0.0?

comment:7 by jng, 17 years ago

Resolution: fixed
Status: newclosed

Removal of FastCGI seems to have done the trick, because I haven't encountered this problem in the RCs or the final release.

Note: See TracTickets for help on using tickets.