Search

WP 7 Map control mouse move event bug in Aerial map mode by soleon

Closed
as External Help for as External

1
0
Sign in
to vote
Type: Bug
ID: 649846
Opened: 3/6/2011 8:18:04 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
The MouseMove event only fires intermittently in Aerial map mode of the Map control for WP7. This problem is very obvious when mouse/finger movement speed is fast. When moving slowly, the event generally fires properly.

This could be a blocking issue for apps that implements drag and drop feature for Pushpins on the map in Aerial mode.

Note, this issue is different and has nothing to do with the MapPan event.
Details (expand)

Visual Studio/Silverlight/Tooling version

Windows Phone Developer Tools

What category (if any) best represents this feedback?

Reliability

Steps to reproduce

1. Start a new WP7 project.
2. Add a Microsoft.Phone.Controls.Maps.Map in root grid:

<my:Map MouseMove="Map_MouseMove" Mode="Aerial"/>

3. Add a debug text box after the map:

<TextBlock x:Name="Debug" Foreground="Red" IsHitTestVisible="False" HorizontalAlignment="Right" VerticalAlignment="Bottom"/>

4. Set Mode="Aerial" for the map.
5. In the Map_MouseMove event handler, simply update the debug text block:

int i = 0;
private void Map_MouseMove(object sender, System.Windows.Input.MouseEventArgs e)
{
Debug.Text = i++.ToString();
}



Text of the debug text block only updates intermittently, especially when mouse/finger movement is fast. The event fires correctly if movement is very slow. This problem does not happen in Road mode.

Product Language

English

Operating System

Windows 7

Operating System Language

English

Actual results

When mouse/finger is moving fast, the MouseMove event only fires intermittently in Aerial map mode of the Map control for WP7.

Expected results

The MouseMove event should fire all the time regardless the movement speed of the mouse/finger.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 6/14/2011 at 12:19 AM
The bug is fixed and verified in build 40219.56. You may try the scenario in the latest build as well.
Posted by Microsoft on 3/6/2011 at 9:13 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.