Skip to content
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

Double clicking on the drag bar to maximize does not update the maximize button icon #1780

Closed
ocalvo opened this issue Jul 2, 2019 · 8 comments · Fixed by #3025
Closed
Assignees
Labels
Area-User Interface Issues pertaining to the user interface of the Console or Terminal Issue-Task It's a feature request, but it doesn't really need a major design. Needs-Tag-Fix Doesn't match tag requirements Product-Terminal The new Windows Terminal. Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release.
Milestone

Comments

@ocalvo
Copy link
Contributor

ocalvo commented Jul 2, 2019

Double clicking on the drag bar to maximize does not update the maximize button icon, the icon remains the same, by contrast, if you click the maximize button the icon does update.

Environment

Windows 10 19H1
Windows Terminal version (if applicable): master

Any other software?

Steps to reproduce

  1. Start Windows Terminal in normal state
  2. Double click the drag bar to maximize the window.

Expected behavior

The maximize button icon is updated

Actual behavior

The maximize button icon does not update.

We are not listening from window state change events from the top level window into the mixmaxclose user control.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 2, 2019
@zadjii-msft zadjii-msft added Area-User Interface Issues pertaining to the user interface of the Console or Terminal Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. labels Jul 2, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jul 2, 2019
@zadjii-msft zadjii-msft added this to the Terminal v0.3 - Preview 2 milestone Jul 2, 2019
@bitcrazed bitcrazed added Issue-Task It's a feature request, but it doesn't really need a major design. and removed Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jul 2, 2019
@gopalrander
Copy link

Debugged and noticed that MinMaxCloseControl::DragBar_DoubleTapped() method is not hit when I double clicked the Drag bar. [But the window maximizes; strange?

@DHowett-MSFT
Copy link
Contributor

@gopalrander the drag bar is actually cut out of the window using a region. It's a complicated story about why exactly we need to do this.

@shanselman
Copy link
Member

Came here to make this bug. ;) Hitting it daily now. Can't we grab the event and delegate it over?

@warmachinesocial
Copy link

warmachinesocial commented Sep 12, 2019

Hi Sir/Madam, I would like to ask you that do you also get an identifier error for both byte and HWND in TitlebarControl.h and TitlebarControl.cpp?? The whole section has lots of error. I just wanna confirm that are you also getting the same error?

Also when i debugged i noticed that DragBar_DoubledTapped method the event isn't detected where other detection of clicking the max,min or close the event is detected.

@filip-hejsek
Copy link

Maximizing the window by dragging it to the top of the screen has the same problem

@zadjii-msft
Copy link
Member

If anyone's interested in fixing this, I think I broke this in #2438.

The trick is that I think we're now treating the titlebar area as HTCAPTION in NonClientIslandWindow, so the mouse presses aren't falling through to the underlying Xaml Island window (the one that draws the TitlebarControl).

We should be able to handle the double-click directly in NonClientIslandWindow directly. I'm a bit curious of why it regressed, but as long as a fix doesn't regress #2028, I'm happy.

@DHowett-MSFT
Copy link
Contributor

Nah, it never was hitting the island here. Double click on a Win32 titlebar always did a maximize by default :)

@ghost ghost added the In-PR This issue has a related PR label Oct 1, 2019
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release. and removed In-PR This issue has a related PR labels Oct 2, 2019
@ghost
Copy link

ghost commented Oct 4, 2019

🎉This issue was addressed in #3025, which has now been successfully released as Windows Terminal Preview v0.5.2762.0.:tada:

Handy links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-User Interface Issues pertaining to the user interface of the Console or Terminal Issue-Task It's a feature request, but it doesn't really need a major design. Needs-Tag-Fix Doesn't match tag requirements Product-Terminal The new Windows Terminal. Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants