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

[CLOSED] [dark shell] Top of title bar not sensitive to double-click when maximized #4904

Open
core-ai-bot opened this issue Aug 29, 2021 · 9 comments

Comments

@core-ai-bot
Copy link
Member

Issue by peterflynn
Tuesday Sep 24, 2013 at 20:45 GMT
Originally opened as adobe/brackets#5327


  1. Maximize Brackets window
  2. Move mouse all the way to top of screen
  3. Double-click

Result: nothing happens

Expected: window is un-maximized (same as if you double-click in the middle of the titlebar)

Other windows apps are sensitive all the way to the very top of the screen. This is important to get the Fitt's Law "infinite edges" effect -- you can throw your mouse vertically to the top without needing any fine positioning.

@core-ai-bot
Copy link
Member Author

Comment by peterflynn
Tuesday Sep 24, 2013 at 20:45 GMT


@JeffryBooher I hit this fairly often, so I'm flagging it a Medium... not sure if it should be required for this sprint or not, though.

@core-ai-bot
Copy link
Member Author

Comment by JeffryBooher
Wednesday Sep 25, 2013 at 02:25 GMT


This is similar to #5269

@core-ai-bot
Copy link
Member Author

Comment by peterflynn
Wednesday Sep 25, 2013 at 03:10 GMT


I think it's a little bit different -- #5269 is only an issue because of the lack of visual separation between menubar and titlebar, and other Windows apps aren't normally draggable from the menubar area. But double-click at the top of a maximized window is common behavior in all Windows apps.

@core-ai-bot
Copy link
Member Author

Comment by JeffryBooher
Wednesday Sep 25, 2013 at 21:34 GMT


@peterflynn it will be fixed with the fix to #5269. It's similar because both issues require some re-work of the WM_NCHITTEST handler which I will do together...

@core-ai-bot
Copy link
Member Author

Comment by peterflynn
Wednesday Sep 25, 2013 at 21:44 GMT


Cool, got it.

@core-ai-bot
Copy link
Member Author

Comment by JeffryBooher
Wednesday Oct 09, 2013 at 15:41 GMT


Actually I think it may not have been fixed with that change after all. Nominating for Sprint 33.

@core-ai-bot
Copy link
Member Author

Comment by JeffryBooher
Friday Oct 11, 2013 at 18:14 GMT


FBNC@peterflynn

@core-ai-bot
Copy link
Member Author

Comment by njx
Tuesday Oct 29, 2013 at 05:05 GMT


@peterflynn - could you confirm this so we can close it out? Thanks.

@core-ai-bot
Copy link
Member Author

Comment by peterflynn
Thursday Oct 31, 2013 at 07:29 GMT


Confirmed fixed... sorry for the delay

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant