Changed APIs for Windows Phone OS 7.1
March 22, 2012
This topic discusses functionality changes and APIs that have been modified for Windows Phone OS 7.1.
For more information about new features in Windows Phone OS 7.1, see:
For information about new APIs in Windows Phone OS 7.1, see:
|
Functionality change |
Windows Phone OS 7.0 behavior |
Windows Phone OS 7.1 behavior |
|---|---|---|
|
Text binding during navigation |
Data-bound text entered in a text box or password box could be lost when navigating away from a page. |
Data-bound text in a text box or password box is updated before navigating away from a page. |
|
Focus in a text box when a physical keyboard is un-deployed |
If the focus is on a text box and a physical keyboard is closed, the text box will retain focus but the on-screen keyboard will not appear. To make the on-screen keyboard appear, the user must tap outside of the text box so that the text box loses focus and then tap back inside the text box so that it regains focus. |
If the focus is on a text box and a physical keyboard is closed, the text box will lose focus and the on-screen keyboard will not appear. The user must tap back inside the text box so that it regains focus and the on-screen keyboard appears. For more information, see How to: Change the On-Screen Keyboard Input Scope in Windows Phone. |
Silverlight for Windows Phone
For general information about changes in Silverlight 4, see Ensuring that Your Silverlight Applications Work with Silverlight 4.
XNA Framework
|
API |
Windows Phone OS 7.0 behavior |
Windows Phone OS 7.1 behavior |
|---|---|---|
|
BeginShowKeyboardInput method |
When an app is tombstoned, the keyboard is dismissed and the callback method is never called with results of the input. |
When you navigate away from an app while the keyboard input is visible, the keyboard will be dismissed. If the app is Activated again, the callback method will be fired. Calling the EndShowKeyboardInput method within the callback method will return null. The developer can then determine whether to display the keyboard input again. |
|
BeginShowMessageBox method |
When an app is tombstoned, the message box is dismissed and the callback method is never called with results of the input. |
When you navigate away from an app while a message box is visible, the message box will be dismissed. If the app is Activated again, the callback method will be fired. Calling the EndShowMessageBox method within the callback method will return null. The developer can then determine whether to display the message box again. |
|
The XNA Framework on Windows Phone OS 7.0 targeted a refresh rate of 30 Hz, regardless of which PresentationInterval you set. |
The XNA Framework on Windows Phone OS 7.1 supports the native device refresh rate, up to 60 Hz. If you set the PresentationParameters.PresentationInterval property to PresentInterval.One, then the PresentInterval.One value is used, targeting the native device refresh rate. |
|
|
Picture.Date property |
The Picture.Date property returns an incorrect date. |
The Picture.Date property returns the correct date. |
Windows Phone
|
API |
Windows Phone OS 7.0 behavior |
Windows Phone OS 7.1 behavior |
|---|---|---|
|
When decoding a JPEG, the value of the maxPixelHeight parameter is incorrectly used to define the maximum width of the decoded JPEG. |
The maxPixelHeight and maxPixelWidth parameters correctly define the maximum height and width of the decoded JPEG. |
|
|
ApplicationBar class |
There is incorrect behavior where an Application Bar button added at run time after a button had been removed at run time would result in items being added to the Application Bar menu but not appearing on the Application Bar as buttons. For example, say:
|
Buttons added at run time after a button has been removed at run time will be added as a button.
|
|
Accelerometer class |
During the Start() and Stop() methods, the accelerometer throws exceptions that other sensors don’t. It can throw UnauthorizedAccessException, ObjectDisposedException, or AccelerometerFailedException exceptions. |
During the Start and Stop methods, the accelerometer does not throw the UnauthorizedAccessException, ObjectDisposedException, or AccelerometerFailedException exceptions. For more information about using the accelerometer, see How to: Get Data from the Accelerometer Sensor for Windows Phone. |
|
PhotoChooserTask and CameraCaptureTask classes |
When the PhotoChooserTask or CameraCaptureTask is canceled by the user or because the Zune application is open, the Error property is not set. |
When the PhotoChooserTask or CameraCaptureTask is canceled by the user or because the Zune application is open, the Error property is set. |
|
PhoneApplicationFrame class |
PhoneApplicationFrame will take action on orientation or visible region change events coming from a PhoneApplicationPage that is in the background. |
PhoneApplicationFrame will not take action on orientation or visible region change events coming from a PhoneApplicationPage that is in the background. This changes the order of how orientation change, visible region change, and navigation events are received when navigating between pages with different supported orientations when the orientation of a page in the background has changed. |
|
Navigating event |
The OnNavigatingFrom(NavigatingCancelEventArgs) method is not called if the navigation is to a page external to the application and if Frame.Navigating sets Cancel to true. Since an external navigation cannot be canceled, navigation will happen regardless of the Cancel value. |
The PhoneApplicationPage.OnNavigatingFrom method is correctly called if navigating to a page external to the application and Frame.Navigating sets Cancel to true. |
