This is a known bug which needs to be resolved in the TabView control, see Issue #2670.ĭragging into a FullScreen Window is not supported.Ĭurrently, the hidden TitleBar of a FullScreen app doesn't appear when performing any drag operation. The right-most tab will disappear when dragging a tab to another window. Clicking on the Taskbar Icon for the app restores the origin window to FullScreen as expected. This also causes an issue if the origin window is FullScreen as the new window is created on the same monitor and takes focus away from the original window, making it look like FullScreen mode has been exited. This is a platform limitation for two reasons, A) we can't determine which monitor the user has dropped the item on, and B) we can't request the window to be opened at a specific location. This sample assumes all Windows are managed by the same process and shares the same implementation for each Window.ĭragging a tab to another monitor/position doesn't open the window on the other monitor/position. This samples assumes the implementor will be using a collection of custom data items bound to the TabView. When constructing a new Window, it needs it's own UI shell to be reconstructed. DependenciesĮach Window runs its own Thread, this has implications on data transfer, Window messaging, and UI Page/Control construction. Requires VS 2017 and Windows 10 version 16299 or above.
It also demonstrates how to place Tabs in the Title Bar of the Application and properly handle Full Screen support.
This sample demonstrates how to use the Windows Community Toolkit's TabView control in combination with Windows Template Studio's Multiple Views support to show how to emulate Microsoft Edge's tear-off tab windowing in your UWP app.
0 kommentar(er)
