If I attempt to have the map in an update panel when using a Google Overlay, any click events cause the map to turn blue (the background color in this case) and stop there.
Remove the update panel and it works fine.
I've attached a test file to show the problem.
I really need to get this to work! Please help.
525-HTMLPage.zip (1.11 KB)
Kirk,
We couldn’t recreate your issue with the code you provided. Can you make sure you are using the latest version (3.1.16) and turn on the script debugging in your browser? If problem still exists please let us know what exception it throws, or it will be great if you can send the whole solution to us (without assemblies) so we can totally recreate your project.
Thanks,
Ben
I'm using VS2005.
I created a new website, added the references to the MapSuite assemblies, dropped in the test code I sent before and it does the same thing.
I've sent attached that solution here.
The page has been tested in IE6, Safari, and FF3 all with the same result.
I've included the source code HTML of the rendered page, one with the map in an update panel, and one without so you can see how it's being served up. Hopefully that will give you a clue as to what is happening.
529-TestMap.zip (119 KB)
Kirk,
The problem is from web.config, replace the web.config file with the one in the samples (along with the product) and everything will be fine.
Thanks,
Ben
Well I couldn’t just replace the web.config in our web application of course, but I did compare them and made some adjustments.
The key seemed to be the <runttime> section which I copied over.
Okay new issue:
The map doesn’t “blue screen” anymore, however when the map is in an update panel my multiview is REALLY slow to respond.
I tried having the map in its own updatepanel and the multiview in its own too, but that seems to make no difference.
Taking the map out of the updatepanel fixes the issue.
So really, I’m back to where I started, sort of.
Is there something I’m missing?
Kirk,
In every postback, we need to transfer whole bunch of json strings to synchronize the states between client and server, this takes some time. Also, the UpdatePanel is just a shortcut for using Ajax in Asp.net. It makes your code much simple and meanwhile it has some performance penalty as it did some extra stuff. There are known issues in our products which might lead to some memory leak, we will try our best to solve it. Also I found when using OpenLayers to manage a big DOM tree, it causes memory leak on client side, that’s another big reason I think.
The better solution is using CallBack, which will most time have better performance than UpdatePanel PostBack. Also, please turn the ClientCache on to avoid reloading same tiles multi times.
If it’s possible, can you send your simple demo to us so we can have a concrete idea how slow it is, as maybe now we are having different understandings on what “slow” means accurately?
Thanks,
Ben