After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 140362 - Double click on window frame edge -> maximize window on that edge
Double click on window frame edge -> maximize window on that edge
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: general
unspecified
Other All
: Low enhancement
: ---
Assigned To: Thomas Thurman
Metacity maintainers list
: 334395 464083 (view as bug list)
Depends on:
Blocks: 358674
 
 
Reported: 2004-04-17 22:38 UTC by Kimball Robinson
Modified: 2020-11-07 12:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Getting the ball rolling for discussion (3.23 KB, patch)
2006-11-14 03:12 UTC, Thomas Thurman
needs-work Details | Review

Description Kimball Robinson 2004-04-17 22:38:18 UTC
I would like to maximize windows in one of the four cardinal directions by 
double clicking on the appropriate window frame.

1.
Event - Double click, on any window frame edge.
2.
Change the window geometry so that edge grows to the edge of the screen.
Comment 1 Elijah Newren 2006-10-01 19:07:31 UTC
*** Bug 334395 has been marked as a duplicate of this bug. ***
Comment 2 Elijah Newren 2006-10-01 19:07:47 UTC
Good drawings in bug 334395.  ;-)
Comment 3 Thomas Thurman 2006-11-14 03:12:36 UTC
Created attachment 76540 [details] [review]
Getting the ball rolling for discussion

How's this for a first attempt? Any comments pro or con?
Comment 4 Bruno Boaventura 2006-11-17 23:15:04 UTC
I have been tested the patch here and it works fine.
Comment 5 Bruno Boaventura 2006-11-18 02:19:39 UTC
:( 
When I click in bottom frame edge, it maximize south and weast.
Comment 6 Thomas Thurman 2006-11-18 19:30:37 UTC
The edge is divided into thirds. The middle third maximises south, the leftmost maximises south and west, and so on. (This is based on the way click-and-drag divides up the edges.)
Comment 7 Bruno Boaventura 2006-11-18 20:50:44 UTC
Sorry by my mistake, Thomas. I have not percept that edge is divided into thirds.
Comment 8 Thomas Thurman 2006-11-18 23:13:04 UTC
no problem at all :)

I will commit this when I get back on Monday, then. Thanks.
Comment 9 Elijah Newren 2006-11-20 06:36:25 UTC
It might be nice to get some usability feedback here.  Similar to how Havoc dislikes the idea of right click on the maximize button for doing things other than showing the window menu, extra functionality like this might dilute the strong correlation of simple reliable actions.  Of course, maybe I just dislike the double-click-on-titlebar causes maximize action and I'm trying to avoid other things like it.  ;-)

As far as the patch goes:
  - Can't include gdk/gtk headers inside core files like display.h
  - If someone double clicked on the left, then on the right, shouldn't
    the window be maximized horizontally?  (Similar for top and bottom and
    vertical maximization?)
Comment 10 Mariano Suárez-Alvarez 2006-11-20 07:48:25 UTC
Honestly, I do not like this. 

In any case, from reading the patch: there seems to be no provision to undo the change, like doubly-ckicking on titlebars maximizes and unmaximizes. Also, should this interact in some way with _NET_WM_STATE? If I double click on the top border (which is not the same as the titlebar!) and in the bottom border, should the window be marked as _NET_WM_STATE_MAXIMIZED_VERT? What should happen if I press the Maximize vertically shortcut in that state? &c.
Comment 11 Thomas Thurman 2006-11-20 17:06:27 UTC
(In reply to comment #9)
> As far as the patch goes:
>   - Can't include gdk/gtk headers inside core files like display.h

aargh, I keep forgetting that. Is there a list somewhere of which files count as core files?

>   - If someone double clicked on the left, then on the right, shouldn't
>     the window be maximized horizontally?  (Similar for top and bottom and
>     vertical maximization?)

Good point.
Comment 12 Thomas Thurman 2007-08-07 01:04:30 UTC
*** Bug 464083 has been marked as a duplicate of this bug. ***
Comment 13 Bradley Whittington 2007-11-25 15:05:26 UTC
Is this bug dead? seems like conversation stagnated, and stalled. I think this is an awesome feature (highly relevant for widescreen and bigger displays). 
Comment 14 Havoc Pennington 2007-11-25 19:06:09 UTC
Seems like we might frame the discussion more broadly, rather than starting with the solution, start with a problem like "have an easy way to snap a window edge out to the screen edge"

double-clicking the frame seems like it requires more hand-eye coordination than I have, to be honest ;-) maybe I need to use a theme with larger frames. It's also a little bit "magic" as Elijah said.

Other ideas, just to throw some out there:

- if you start dragging an edge and then kind of "throw" with the mouse it throws the edge to the side of the screen (this is hard to program so it feels good, though)

- if you click while holding some modifier, it goes to the edge (wait, Shift already does this! doh!)

- if you press an arrow key while resizing with mouse, it snaps the edge to the next snap-point that Shift would have chosen, or alternatively always snaps to screen edge

Any other ideas?

Holding Shift while resizing is pretty close to a decent solution already, try it out. I had forgotten about that feature until I was halfway through typing this.


Comment 15 Bradley Whittington 2007-11-25 21:14:50 UTC
Well there we go, Shift drag is exactly what I wanted. My brain assumed a double-click on a handle would maximise in the direction. The only thing lacking seems to be window memory for how it was (i.e. shift drag from extent back should snap to where it was).

Okay, well, shift-drag does what I was looking for, but I still want to +1 a double click handle (to me it fits in with how double click title bar maximises), and shift-drag seems a bit obscure, but then rtfm eh?

cool.
Comment 16 André Klapper 2020-11-07 12:36:27 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all
old feature requests in Bugzilla which have not seen updates for many years.

If you still use metacity and if you are still requesting this feature in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/

Thank you for reporting this issue and we are sorry it could not be implemented.