Skip to content

Latest commit

 

History

History
50 lines (41 loc) · 6.53 KB

breaking-changes.md

File metadata and controls

50 lines (41 loc) · 6.53 KB
titledescriptionms.topicms.datekeywordsms.localizationpriority
Breaking changes in the Windows App SDK
If you're migrating an app to Windows App SDK 1.0 from 0.8, the breaking changes listed here might affect you. Changes are grouped by technology area, such as input and MRT Core.
article
04/19/2024
windows, windows app development, Windows App SDK
medium

Breaking changes - Project Reunion 0.8 to Windows App SDK 1.0

If you're migrating an app to Windows App SDK 1.0 from Project Reunion 0.8, the breaking changes listed here might affect you. Changes are grouped by technology area, such as input and MRT Core.

Input

API changes from 0.8 to 1.0

Behavior changes from 0.8 to 1.0

  • Underlying input system infrastructure upgraded to use an independent message queue for processing.
    • Supports low-latency off-UI-thread input such as inking.
    • Fully supports lifted interaction tracker APIs such as Microsoft.UI.Composition.VisualInteractionSource (and others).
    • Fully supports hover input for off-thread input delivery (this was a limitation in 0.8).
    • System input messages, such as WM_POINTERDOWN, are no longer visible through Win32 APIs on the UI thread as they are routed to an independent message queue inside the infrastructure.
  • PointerPoint is now agile and can be accessed on any thread.
  • PointerPoint objects can no longer be constructed statically from a pointer ID.
  • XAML-based drag and drop operations fully support mouse, touch, and pen input (0.8 used pen-to-mouse downleveling).
  • Direct use of Windows.ApplicationModel.DataTransfer.DragDrop.Core.CoreDragOperation will no longer work on the UI thread. XAML drag and drop must be used instead.

MRT Core

MRT Core APIs have moved from the Microsoft.ApplicationModel.Resources namespace to the Microsoft.Windows.ApplicationModel.Resources namespace.

close