When MapControl placed inside ScrollViewer pan not working

ItamarKcholi

Hi,

When i place the map control inside a ScrollViewer the pan is not working (i still receive MouseMove and the zoom by mouse wheel still working as well as the esri:Navigation, esri:OverviewMap etc..)

You can recreate this issue with the following code:

<Window x:Class="TestMapScrollViewerIssue.MainWindow"
     xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:esri="http://schemas.esri.com/arcgis/client/2009"
        Title="MainWindow" Height="350" Width="525">
    <Grid>

        <ScrollViewer VerticalScrollBarVisibility="Auto"
                      Height="400"
                      Grid.Row="1"
                      Background="White">

            <!-- Map Control-->
            <esri:Map x:Name="_mapControl"
                      UseAcceleratedDisplay="False">

                <!-- * Tiled Basemap Layer(s) * -->

                <!-- ArcGIS Online Tiled Basemap Layer -->
                <esri:ArcGISTiledMapServiceLayer ID="arcGISTiledMapServiceLayer"
                                                 Url="http://services.arcgisonline.com/ArcGIS/rest/services/World_Topo_Map/MapServer" />
            </esri:Map>
        </ScrollViewer>
    </Grid>
</Window>

Please let me know if i am doing something wrong.

Thanks,
Itamar

BjørnarSundsbø

I also ran into this issue when working with a third party component that also set e.Handlet = true. Was able to override that behavior by extending the class that did this. However, it seems to me that the logic of Map is flawed. Where it should override OnMouseLeftButtonDown, it subscribes to the event. In that case, it doesn't follow the natural flow of overriding this event. A suggested fix for this issue would be to pass in the e.Handled when dispatching the delegate for performing the logic.

There are probably reasons why the design is as it is, but is this something that will be fixed? I am yet on version 2.x of the control, so I have not been able to verify if it has been resolved in 10.1.