This article describes an update that resolves some issues about Silverlight for Windows Embedded (SWE) application for Windows Embedded Compact 2013 on a Windows Embedded Compact 2013-based device. This hotfix requires that all previously issued updates for this product have also been installed.
This update fixes the following issues:
This update fixes the following issues:
- Assume that you use RegisterXamlObject to register an Activex control in a Silverlight for Windows Embedded (SWE) application on a Windows Embedded Compact 2013-based device. When you animate a custom DependencyProperty in a storyboard for the Activex control, the animation timeline does not run. Additionally, the other timelines in the same storyboard do not run unless the custom DependencyProperty is removed.
- Consider the following scenario:
- You have a Silverlight for Windows Embedded (SWE) application on a Windows Embedded Compact 2013-based device that contains a Visual C++ 2008 and a Blend XAML part.
- The application contains a ListBox or a ComboBox control.
- You use a text box to display an item that is selected.
- You run the application and use a touch gesture to select a list item
- Assume that you have a Microsoft Silverlight for Windows Embedded (SWE) application that contains a ListBox control on a Windows Embedded Compact 2013-based device. There are grouped RadioButtons in the ListBox control and a RadioButton is selected. When you remove and re-add the ListBox control to the visual tree, the checked button remains in checked state and does not clear if another RadioButton from the same group is selected.
- Assume that you have a Microsoft Silverlight for Windows Embedded (SWE) application on a Windows Embedded Compact 2013-based device. When you assign a TemplateBinding markup extension to a custom PropertyBag dependency property on a custom control, the application cannot display all UI elements correctly. Additionally, you receive the following error message in the debug output:[XR] ObjectFactory::WarnForDataBindingFailure - DataBinding Warning -- Binding failure, Control=?Control, Target property=TestContent, Binding Path=BoundPropertyBag, HRESULT=0x80070057
[XR] XRVisualHost::PaintElementTree - Failed to Draw the element tree in HWND 0xfe170002. Error code 0x80070057 - When you use a Silverlight for Windows Embedded (SWE) application in Windows Embedded Compact 2013. You receive the following binding warning during the initialization of the data binding on SelectedItem:[XR] ObjectFactory::WarnForDataBindingFailure - DataBinding Warning -- Binding failure, Control=ListBox, Target property=SelectedItem, Binding Path=MySelectedItem, HRESULT=0x80070057After the data is bound, when you try to set the property value in a UserControl control, an access violation occurs.
- Consider the following scenario:
- You have a Microsoft Silverlight for Windows Embedded application on a Windows Embedded Compact 2013-based device.
- The device has a single-core processor.
- You enable the following board support package (BSP) environment variable in order to support OpenGL hardware acceleration for Silverlight for Windows Embedded: BSP_XRPLUGIN_OPENGL .
- When you have a Silverlight for Windows Embedded application that uses OpenGL ES in Windows Embedded Compact 2013, the screen updates slowly. This issue occurs because the entire texture is always updated, even if only a smaller area needs to be updated.
- Assume that you have a Microsoft Silverlight for Windows Embedded (SWE) application on a Windows Embedded Compact 2013-based device. You set the SelectedIndex binding of a ListBox to -1 and the DataContext to null. When you set the same object as DataContext again, the selection is lost. The expect result is that setting the DataContext to null should not trigger any changes on the DataContext properties.
Note SelectedItem bound property is set to null when the DataContext is set to null. - Assume that you run a Microsoft Silverlight for Windows Embedded (SWE) application on a Windows Embedded Compact 2013-based device. When you register a gesture event handler on a control (for example the Canvas or Button control), your application code is called in the event handler for all gesture messages except the GID_END one.