-
-
Notifications
You must be signed in to change notification settings - Fork 897
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
Master layout: choosing placement of master area #1059
Labels
enhancement
New feature or request
Comments
Closed
proycon
added a commit
to proycon/Hyprland
that referenced
this issue
Dec 10, 2022
This implement a per workspace 'orientation' that can be set to left, right, top or bottom. Reflecting placement of the master area. Left (default) and right are horizontal layouts, top and bottom produce vertical layouts. Orientation can be switched with: 'hyprctl dispatch layoutmsg orientationleft'
proycon
added a commit
to proycon/Hyprland
that referenced
this issue
Dec 10, 2022
…prwm#1059) adds orientationnext and orientationprev
proycon
added a commit
to proycon/Hyprland
that referenced
this issue
Dec 10, 2022
…pace-specific data (hyprwm#1059) Accommodates the new orientation data Also introduced a master:orientation setting to set the default orientation
proycon
added a commit
to proycon/Hyprland
that referenced
this issue
Dec 10, 2022
This implement a per workspace 'orientation' that can be set to left, right, top or bottom. Reflecting placement of the master area. Left (default) and right are horizontal layouts, top and bottom produce vertical layouts. Orientation can be switched with: 'hyprctl dispatch layoutmsg orientationleft'
proycon
added a commit
to proycon/Hyprland
that referenced
this issue
Dec 10, 2022
This implement a per workspace 'orientation' that can be set to left, right, top or bottom. Reflecting placement of the master area. Left (default) and right are horizontal layouts, top and bottom produce vertical layouts. Orientation can be switched with: 'hyprctl dispatch layoutmsg orientationleft'
proycon
added a commit
to proycon/hyprland-wiki
that referenced
this issue
Dec 10, 2022
vaxerski
pushed a commit
that referenced
this issue
Dec 10, 2022
…1202) * Implemented choosing placement of master area (#1059) This implement a per workspace 'orientation' that can be set to left, right, top or bottom. Reflecting placement of the master area. Left (default) and right are horizontal layouts, top and bottom produce vertical layouts. Orientation can be switched with: 'hyprctl dispatch layoutmsg orientationleft'
vaxerski
pushed a commit
to hyprwm/hyprland-wiki
that referenced
this issue
Dec 10, 2022
spikespaz
pushed a commit
to spikespaz-contrib/hyprland
that referenced
this issue
Dec 12, 2022
…yprwm#1202) * Implemented choosing placement of master area (hyprwm#1059) This implement a per workspace 'orientation' that can be set to left, right, top or bottom. Reflecting placement of the master area. Left (default) and right are horizontal layouts, top and bottom produce vertical layouts. Orientation can be switched with: 'hyprctl dispatch layoutmsg orientationleft'
spikespaz
pushed a commit
to spikespaz-contrib/hyprland
that referenced
this issue
Dec 12, 2022
…yprwm#1202) * Implemented choosing placement of master area (hyprwm#1059) This implement a per workspace 'orientation' that can be set to left, right, top or bottom. Reflecting placement of the master area. Left (default) and right are horizontal layouts, top and bottom produce vertical layouts. Orientation can be switched with: 'hyprctl dispatch layoutmsg orientationleft'
scorpion-26
pushed a commit
to scorpion-26/Hyprland
that referenced
this issue
Dec 15, 2022
…yprwm#1202) * Implemented choosing placement of master area (hyprwm#1059) This implement a per workspace 'orientation' that can be set to left, right, top or bottom. Reflecting placement of the master area. Left (default) and right are horizontal layouts, top and bottom produce vertical layouts. Orientation can be switched with: 'hyprctl dispatch layoutmsg orientationleft'
spikespaz
pushed a commit
to spikespaz-contrib/hyprland
that referenced
this issue
Dec 25, 2022
…yprwm#1202) * Implemented choosing placement of master area (hyprwm#1059) This implement a per workspace 'orientation' that can be set to left, right, top or bottom. Reflecting placement of the master area. Left (default) and right are horizontal layouts, top and bottom produce vertical layouts. Orientation can be switched with: 'hyprctl dispatch layoutmsg orientationleft'
spikespaz
pushed a commit
to spikespaz-contrib/hyprland
that referenced
this issue
Jan 13, 2023
…yprwm#1202) * Implemented choosing placement of master area (hyprwm#1059) This implement a per workspace 'orientation' that can be set to left, right, top or bottom. Reflecting placement of the master area. Left (default) and right are horizontal layouts, top and bottom produce vertical layouts. Orientation can be switched with: 'hyprctl dispatch layoutmsg orientationleft'
spikespaz
pushed a commit
to spikespaz-contrib/hyprland
that referenced
this issue
Jan 20, 2023
…yprwm#1202) * Implemented choosing placement of master area (hyprwm#1059) This implement a per workspace 'orientation' that can be set to left, right, top or bottom. Reflecting placement of the master area. Left (default) and right are horizontal layouts, top and bottom produce vertical layouts. Orientation can be switched with: 'hyprctl dispatch layoutmsg orientationleft'
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I like using the master layout in hyprland (used to it coming from dwm) and I like the very recent improvement to it (master swap toggle). The only issue I still have is that it's currently not ideal on a (second) vertical/portrait monitor, where the master and slave areas are split vertically, leading to two narrow areas.
A possible solution to solve this and make the master layout more powerful would be if the user could choose (per workspace) where to place the master area. We could envision a
masterplacement
command for the layoutmsg dispatcher The current implementation would correspond tomasterplacement left
, but additionally users could opt forright
(master right, slaves left split horizontally ),top
(master top, slaves on bottom split vertically) andbottom
(master bottom, slaves on top split vertically).Has some relation with #622, which wasn't deemed feasible in the current implementation; this would address the issue whilst sticking to a single layout.
I might have a try at implementing this myself if the idea is welcomed...
The text was updated successfully, but these errors were encountered: