Why does it take so long to change Layer Themes?
I have an HTML5 (4.5.1/2.6.1) site with a number of Layer Themes. I'm finding it takes almost 4 seconds to change from one to the other. In an almost identical Silverlight site, it is almost instantaneous... Any idea why?
https://maps.srcity.org/Html5Viewer/Index.html?viewer=SantaRosaMap
0
-
Mike,
I noticed that as well after I upgraded to Essentials 4.5.1 / GVH 2.6.1. I found that if I deselect (turn off) all layers that are on the "All Available Layers" tab with the exception of Base Maps, performance seems to increase a little.
Rick0 -
Richard,
Our folks use the All Available Layers, and I have it currently configured to only display a few boundary and label layers at open. I also use layer groups extensively, where the group may be unchecked, but the layers inside may have some or all checked to be visible when the group is checked - would that have an effect? I don't really want to hae to turn all layers to invisible, since that would casue confusion for my users...0 -
I would create a new GVH app within your site to test turning off the "All Available Layers" and seeing if you see any changes. Just use a different layer theme as the default.
We also use Layer Themes extensively. I set the Layer theme (1) just below the "All Available Layers" as the default. With the GVH 2.6.1 update, I was noticing that the layers that were switched ON to visible in the All Available Layers theme were showing themselves, then turning off as the Default layer theme opened. My fix was to turn off the layers in "All Available Layers". I was wondering if this bug had to do with our applications architecture. Our sites that have the GVH application inside them do not natively have any layers configured in them. We use referenced sites to bring in the data in. That way if I have to change a layer, I just change the layer in the referenced site and the changes replicate in all of the other GVH application sites.
Rick0 -
We already do use a different theme as the default. Most folks tend to only use one theme for 95% of their time, and I have launch urls for them that open the site directly to their theme. So this isn't a huge issue for me, just something that I noticed. There are quite a number of little quirks with HTML5 that can slow things down. LG seems to be working on them as they find them. I ended up submitting this as an official case, and I've sent them a Fiddler capture. I'll post later once they tell me more. 0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
4 Kommentare