werabargains.blogg.se

Here's some typical UWP code to display a ContentDialog. The code examples below use ContentDialog, but you can apply exactly the same techniques to displaying a Popup object. If in your UWP app you're using the Windows.UI. or Windows.UI. classes, then this section contains info to help you migrate that code. For more info, and code examples, see Display WinRT UI objects that depend on CoreWindow. To use DataTransferManager.ShowShareUI in your Windows App SDK app, you need to associate the Share UI with your window. Windows::ApplicationModel::DataTransfer::DataTransferManager::ShowShareUI() Windows::ApplicationModel::DataTransfer::DataRequestedEventArgs const& args)Īrgs.Request().Data().Properties().Title(L"In a UWP app.") Īrgs.Request().Data().SetText(L".display the user interface for sharing content with another app.") Īrgs.Request().Data().RequestedOperation(Windows::ApplicationModel::DataTransfer::DataPackageOperation::Copy) in a UWP appĪuto width ĭataTransferManager.DataRequested((Windows::ApplicationModel::DataTransfer::DataTransferManager const& /* sender */, That property isn't supported in the Windows App SDK, so this section describes how to port UWP code that uses Window.Current. This section applies if you're using the Windows.UI. property in your UWP app. In the Windows App SDK, the AcrylicBrush always samples from the app content. You may need to refactor your Visual State Manager and Page.Resources XAML markup.

To use DataTransferManager APIs, you need to associate them with your window.įor ContentDialog and Popup, you need to set their XamlRoot property. You need to set your window's handle ( HWND) on a MessageDialog, and on Pickers.

And the CoreDispatcher.RunAsync method migrates to DispatcherQueue.TryEnqueue. The Window.Current property migrates to App.Window. Summary of API and/or feature differences This topic shows how to migrate your user interface (UI) code, including migrating to the Windows UI Library (WinUI) 3.