nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to make Legend control refresh the info?

GeorgeFaraj

How can I make the Legend control refresh the label / image if I change the DisplayName and Renderer properties for a Layer? I've been able to do it by setting the Map to null, then setting it back again. But this resets the tree back to everything expanded. I just want it to update the info. Is this possible?

Find more posts tagged with

Runtime SDK for WPF

Accepted answers

DominiqueBroux

The workaround for now might be you to set the Label of the corresponding LayerItemViewModel when you change the DisplayName.

An easier workaround might also be to set ShowLegend to false and then again to true after changing the DisplayName.

layer.DisplayName= "newDisplayName"; layer.ShowLegend=false; layer.ShowLegend=true;

All comments

DominiqueBroux

The legend is supposed to refresh itself automatically when a property of the layers changes.
However I noticed a bug: when changing the 'DisplayName', the legend is not refreshed.

The workaround for now might be you to set the Label of the corresponding LayerItemViewModel when you change the DisplayName.

We'll try to get it fixed in the API ASAP.

Concerning the renderer, I was not able to reproduce the issue. When changing the layer renderer, the legend seems to refresh (if you found out a use case where that doesn't happen, a workaround might to call Legend.Refresh()).

Thanks for reporting that.

DominiqueBroux

The workaround for now might be you to set the Label of the corresponding LayerItemViewModel when you change the DisplayName.

An easier workaround might also be to set ShowLegend to false and then again to true after changing the DisplayName.

layer.DisplayName= "newDisplayName"; layer.ShowLegend=false; layer.ShowLegend=true;

GeorgeFaraj

Thank you, Dominique, that workaround worked. I haven't tried changing the renderer yet, but I figured since the name didn't change, I might have problems with the renderer too. Glad that you could find the cause of the bug.

Thanks,
George

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.