-
Notifications
You must be signed in to change notification settings - Fork 628
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating TabView to consume tear-out APIs #1574
Open
llongley
wants to merge
20
commits into
main
Choose a base branch
from
user/llongley/ConsumingTabTearOut
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Is it intended to merge into Scott's 1.6 Experimental1 branch? |
Scottj1s
requested changes
Jul 23, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
per Karen, target branch looks like it needs updating
llongley
force-pushed
the
user/llongley/ConsumingTabTearOut
branch
from
August 13, 2024 23:49
2377d8e
to
5458f50
Compare
Updated to target the main branch instead. |
Scottj1s
reviewed
Aug 26, 2024
Scottj1s
reviewed
Aug 26, 2024
Fixes #1622 |
llongley
commented
Sep 24, 2024
/azp run |
2 similar comments
/azp run |
/azp run |
- Removing unneeded MSBuild target. - Fixing an issue causing Windows.UI.Xaml.dll to be loaded. -
… a third tier in the tree view. - Added the locally-built package names for the app to the list. - Changed so we retrieve the program files path from an environment variable instead of hard-coding it to the C drive.
karkarl
force-pushed
the
user/llongley/ConsumingTabTearOut
branch
from
September 27, 2024 18:29
8ace97c
to
ebe5fab
Compare
/azp run |
/azp run |
/azp run |
/azp run |
/azp run |
/azp run |
/azp run |
/azp run |
/azp run |
/azp run |
This reverts commit 44824c6.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These changes update WinUI Gallery to consume the new TabView tear-out APIs in WASDK experimental 1, instead of using the WinRT drag-and-drop APIs. This makes it so that tab tear-out immediately creates a new window that the user starts to drag, rather than waiting for a drop to create the new window.
While I was here, I also added a change to enable running WinUI Gallery as an unpackaged app, which appeared to previously not be properly functional.