Last Updated: 03 May 2019 16:50 by ADMIN
Martin Ivanov
Created on: 27 Jul 2016 13:56
Category: Map
Type: Bug Report
Map: The providers order in the visual tree is wrong when the map source of a provider is updated at runtime
When you have two providers - BingMapProvider and custom TiledProvider - and the map source of the second provider (the custom one) is changed, the updated provider is drawn under the provider defined before it in the Providers collection (the BingMapProvider).

To work this around you can call the BingMapProvider's SetMapSource() method after the source of the custom provider is changed.

// set the custom provider source
Martin Ivanov
Posted on: 03 May 2019 16:50
Hello Jason,

Thank you for the new information. At this point the mentioned feedback items are not included for the planning. However, I will bring them to the corresponding team for discussion. Anyway, I cannot promise anything and that's why I would recommend you to continue following the feedback item. This way once its status changes you'll get notified by email.

Please excuse us for the inconvenience.

Martin Ivanov
Progress Telerik
Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Jason D
Posted on: 26 Apr 2019 20:25

I guess not many people are using custom providers. However this is super high priority for us. I moved all of our map code to be completely in WPF. When I did that, this issue re-appeared. I spent 1-2 weeks trying to work around it. The SetMapSource solution does not work for me. The workaround I posted below works most of the time, but not all. If this could be fixed in conjuction with Providers binding, the whole thing would just magically work in a nice MVVM fashion and I could delete a lot of code. I have not been able to reproduce using a sample project and it's very hard to find the time to attempt it.


Posted on: 16 Aug 2018 12:36
Hi Jason,

Thank you for sharing your solution here. I hope this would help also someone else.

As for the issue, currently this is not fixed and it isn't included in our current planning. I would suggest you to follow the feedback item so that you are notified as soon as there is any update on i ts status.

Martin Ivanov
Technical Support Engineer
Jason D
Posted on: 16 Mar 2018 14:54
I upgraded from 2014 to 2018 and this problem still exists. However, I found another workaround due to my code order. If the BingMapProvider is inserted at position 0 *after* the custom provider has already been added, the problem goes away. I noticed this because my Bing provider is added last because I don't know which base map provider I'll be using until runtime. I confirmed this workaround works for both 2014 and 2018 versions.