InformationLayer.GetBestView() give wrong result with data binded MapPinPoint

2 posts, 0 answers
  1. Gauthier
    Gauthier avatar
    3 posts
    Member since:
    Sep 2013

    Posted 06 Dec 2013 Link to this post

    Hi,



    I tried to use the InformationLayer.GetBestView(items), but it requires to be called several times to have correct result.

    (If it is called with MapPinPoint)



    Here is the template of the MapPinPoint :



    <DataTemplate x:Key="ObstructionPointItemTemplate"><br>
                <telerik:MapPinPoint <br>
                    BorderBrush="{StaticResource ObstructionPointColor}"<br>
                    Template="{StaticResource PointControlTemplate}" <br>
                    telerik:MapLayer.Location="{Binding }"><br>
                    <telerik:MapLayer.HotSpot><br>
                        <telerik:HotSpot X="0.5" Y="0.5" /><br>
                    </telerik:MapLayer.HotSpot><br>
                </telerik:MapPinPoint><br>
    </DataTemplate>






    In order to eliminate any side effects with the databinding or the map provider latency, the call to 'GetBestView' is made by an event handler attached to a user interaction (MouseRightButtonDown).



    I have a lightweight VS2012 solution were I reproduced the issue, if needed





    Can you please help me ?





    Thanks in advance
  2. Andrey
    Admin
    Andrey avatar
    1681 posts

    Posted 10 Dec 2013 Link to this post

    Hi Gauthier,

    In the Q2 2013 release we've introduced new visualization engine in RadMap. It has been designed from scratch to have better performance. The new engine is based on the VisualizationLayer class. This is why I would recommend giving it a try. You can find more information and examples of the new layer here:

    The VisualizationLayer also contains the GetBestView() method and it should work correctly in your case. Please try it our and let us know if it helps.

    Regards,
    Andrey Murzov
    Telerik

    TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.



    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.



    Sign up for Free application insights >>
  3. UI for WPF is Visual Studio 2017 Ready
Back to Top