-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Enable dragging with the entire titlebar #1948
Conversation
Don't do anything in NCPAINT. If you do, you have to do everything. But the whole point of DwmExtendFrameIntoClientArea is to let you paint the NC area in your normal paint. So just do that dummy. * This doesn't transition across monitors. * This has a window style change I think is wrong. * I'm not sure the margins change is important.
I'm not entirely sure why. But if we only update the titlebar drag region when that actually changes, it's a _lot_ smoother. I'm not super happy with the duplicated work in _UpdateDragRegion and OnSize, but checking this in in case I can't figure that out.
…ie/f/newtab-btn-float-left
…tton * Make the new tab button transparent, to see how that looks * Make sure the TabView doesn't push the MMC off the window
* The TitlebarControl is owned by the NCIW. It consists of a Content, DragBar, and MMCControl. * The App instatntiates a TabRowControl at runtime, and either places it in the UI (for tabs below titlebar) or hangs on to it, and gives it to the NCIW when the NCIW creates its UI. * When the NCIW is created, it creates a grid with two rows, one for the titlebar and one for the app content. * The MMCControl is only responsible for Min Max Close now, and is closer to the window implementation. * The drag bar takes up all the space from the right of the TabRow to the left of the MMC * Things that **DON'T** work: - When you add tabs, the drag bar doesn't update it's size. It only updates OnSize - The MMCControl's Min and Max buttons don't seem to work anymore. - They should probably just expose their OnMinimizeClick and OnMaximizeClick events for the Titlebar to handle minimizing and maximizing. - The drag bar is Magenta (#ff00ff) currently. - I'm not _sure_ we need a TabRowControl. We could probably get away with removing it from the UI tree, I was just being dumb before.
I forgot to plumb the window handle through
…ie/f/newtab-btn-float-left # Conflicts: # src/cascadia/WindowsTerminal/NonClientIslandWindow.cpp
…-btn-float-left # Conflicts: # src/cascadia/WindowsTerminal/NonClientIslandWindow.cpp
@@ -53,10 +54,11 @@ namespace winrt::TerminalApp::implementation | |||
// (which is a root when the tabs are in the titlebar.) | |||
Windows::UI::Xaml::Controls::Control _root{ nullptr }; | |||
Microsoft::UI::Xaml::Controls::TabView _tabView{ nullptr }; | |||
Windows::UI::Xaml::Controls::Grid _tabRow{ nullptr }; | |||
|
|||
TerminalApp::TabRowControl _tabRow{ nullptr }; |
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.
this was not necessary any longer, yes?
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.
technically yes, the TabRowControl isn't totally necessary, but I was inclined to keep it, to keep each piece more atomic. If you feel strongly, I can change it back
|
||
Windows::UI::Xaml::UIElement TitlebarControl::Content() | ||
{ | ||
return ContentRoot().Children().Size() > 0 ? ContentRoot().Children().GetAt(0) : nullptr; |
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.
this is technically something you should use a control template and a template binding for.
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.
so that people can do <TitleBar>Whatever</TitleBar>
and it will put Whatever in the Content
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.
That's certainly the direction I was going with this, but I wanted to try and split that into a different task - this one's already getting hefty. I can file a follow-up issue, yea?
…-btn-float-left # Conflicts: # src/cascadia/TerminalApp/TerminalApp.vcxproj
Co-Authored-By: Michael Niksa <[email protected]>
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.
I like it. A lot.
<ColumnDefinition Width="Auto"/> | ||
</Grid.ColumnDefinitions> | ||
|
||
<Grid x:Name="ContentRoot" Grid.Column="0" /> |
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.
Try out a ContentPresenter
. Its sole job is to present content; perhaps it'll help you not have to interact with Children
😄
// calling. We know that our content is a Grid, so we don't need to worry | ||
// about this. | ||
const auto fwe = content.try_as<winrt::Windows::UI::Xaml::FrameworkElement>(); | ||
if (fwe) |
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.
if (fwe) | |
if (const auto fwe = ...) |
Some thoughts about the Min/Max/Close buttons, and supporting FullScreen or Tablet Mode Some properties to consider for this TitlebarControl. This could be also be useful for the Settings UI, if it is presented in a window.
Which would hide those buttons if you wanted to make a settings screen which only shows a close button. Also consider how these TitleBar Controls will handle FullScreen/Tablet Mode |
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.
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
* This definitely works for getting shadow, pointy corners back Don't do anything in NCPAINT. If you do, you have to do everything. But the whole point of DwmExtendFrameIntoClientArea is to let you paint the NC area in your normal paint. So just do that dummy. * This doesn't transition across monitors. * This has a window style change I think is wrong. * I'm not sure the margins change is important. * The window style was _not_ important * Still getting a black xaml islands area (the HRGN) when we switch to high DPI * I don't know if this affects anything. * heyo this works. I'm not entirely sure why. But if we only update the titlebar drag region when that actually changes, it's a _lot_ smoother. I'm not super happy with the duplicated work in _UpdateDragRegion and OnSize, but checking this in in case I can't figure that out. * Add more comments and cleanup * Try making the button RightCustomContent * * Make the MinMaxClose's drag bar's min size the same as a caption button * Make the new tab button transparent, to see how that looks * Make sure the TabView doesn't push the MMC off the window * Create a TitlebarControl * The TitlebarControl is owned by the NCIW. It consists of a Content, DragBar, and MMCControl. * The App instatntiates a TabRowControl at runtime, and either places it in the UI (for tabs below titlebar) or hangs on to it, and gives it to the NCIW when the NCIW creates its UI. * When the NCIW is created, it creates a grid with two rows, one for the titlebar and one for the app content. * The MMCControl is only responsible for Min Max Close now, and is closer to the window implementation. * The drag bar takes up all the space from the right of the TabRow to the left of the MMC * Things that **DON'T** work: - When you add tabs, the drag bar doesn't update it's size. It only updates OnSize - The MMCControl's Min and Max buttons don't seem to work anymore. - They should probably just expose their OnMinimizeClick and OnMaximizeClick events for the Titlebar to handle minimizing and maximizing. - The drag bar is Magenta (#ff00ff) currently. - I'm not _sure_ we need a TabRowControl. We could probably get away with removing it from the UI tree, I was just being dumb before. * Fix the MMC buttons not working I forgot to plumb the window handle through * Make the titlebar less magenta * Resize the drag region as we add/remove tabs * Move the actual MMC handling to the TitlebarControl * Some PR nits, fix the titlebar painting on maximize * Put the TabRow in our XAML * Remove dead code in preparation for review * Horrifyingly try Gdi Plus as a solution, that is _wrong_ though * Revert "Horrifyingly try Gdi Plus as a solution, that is _wrong_ though" This reverts commit e038b5d. * This fixes the bottom border but breaks the titlebar painting * Fix the NC bottom border * A bunch of the more minor PR nits * Add a MinimizeClick event to the MMCControl This works for Minimize. This is what I wanted to do originally. * Add events for _all_ of the buttons, not just the Minimize btn * Change hoe setting the titlebar content works Now the app triggers a callcack on the host to set the content, instead of the host querying the app. * Move the tab row to the bottom of it's available space * Fix the theme reloading * PR nits from @miniksa * Update src/cascadia/WindowsTerminal/NonClientIslandWindow.cpp Co-Authored-By: Michael Niksa <[email protected]> * This needed to be fixed, was missed in other PR nits * runformat wait _what_ * Does this fix the CI build?
🎉 Handy links: |
Summary of the Pull Request
If a picture is worth 1000 words, then this is
15000 words/secondlike 18000 words (getting a gif below 10MB was harder than I thought)References
This is a bunch of the work in #1625 and #1375.
PR Checklist
Detailed Description of the Pull Request / Additional comments
This is done with a major change to the
NonClientIslandWindow
, and theMinMaxControl
. I've introduced a new XAML control, theTitlebarControl
. TheTitlebarControl
consists of three parts - Content, Drag Area, andMinMaxControl
. TheMinMaxControl
is now owned by theTitlebarControl
, and it does pretty much nothing on it's own. All the hwnd handling has moved up to theTitlebarControl
. TheMinMaxControl
now exists simply as a control with caption buttons.Instead of the
App
owning theMinMaxControl
, and the titlebar existing as part of the TerminalPage, theTitlebarControl
is now owned by theNonClientIslandWindow
. TheNonClientIslandWindow
will initialize it's own UI consisting of a titlebar row and a content row. It'll place aTitlebarControl
instance in its titlebar row. It'll also ask theApp
for content to place in both the client area and the titlebar. When the app is resized, or the titlebar content is resized, theNonClientIslandWindow
will update its drag area. TheNonClientIslandWindow
can also communicate directly with theTitlebarControl
, without needing to go through theApp
to do so. In the future, This should make future windowing-related bugs easier to fix.TODOs
MARGIN
s passed toDwmExtendframIntoClientArea
, the amount changes. This regressed between 1905852 and 96c5da2. I want to track this down before we check this in.60a444c7b8cf10b9cc819021978102e8389 (wait there's only f4e02d8 between those two??)#000000
, the window frame bleeds through entirely. For example, I have a bright cyan accent color. If I change thebackgroundColor
to#ff00000
, then the single pixel at the bottom will appear almost white: