aboutsummaryrefslogtreecommitdiffstats
path: root/sway/output.c
Commit message (Collapse)AuthorAge
* Move sway's internal tree code to sway/tree/Libravatar Drew DeVault2017-11-11
|
* Add output wrappingLibravatar Daniel Kessler2017-01-13
| | | | | | | | | This fixes issue #733. Now if the user focuses output right but is at the rightmost monitor, the focus will wrap the the leftmost monitor. This commit adds a new function, swayc_opposite_output, which selects the opposite output given a position and a direction. Now, when calling output_by_name, we first check if there is an adjacent output to switch to. If that fails, we call swayc_opposite_output to handle wrapping.
* Reorganize includesLibravatar Drew DeVault2016-09-01
|
* Update hidpi support to latest wlc APILibravatar Drew DeVault2016-07-28
|
* implement stable sort for listsLibravatar Zandr Martin2016-06-02
| | | | also change sort_workspaces() to use it
* remove alphabetic sorting from sort_workspacesLibravatar Zandr Martin2016-05-28
| | | | also add a couple missing spaces to container.c (unrelated)
* Implement sort_workspaces() function for outputs.Libravatar Zandr Martin2016-05-27
| | | | This seems to have resolved issue #669 for me.
* output: Support multiple adjacent outputs.Libravatar S. Christoffer Eliesen2015-11-16
| | | | | | | | | | | | | | | | | | | | | | | | | | When querying for an adjacent output we now need an absolute position in order to know which adjacent output that matches. (The position is either the current mouse position or the center of the currently focused container, depending on context.) If two outputs have one edge each that at least partially align with each other they now count as adjacent. Seamless mouse is affected by this and now properly moves and positions itself between outputs with "uneven" placement (as long as they have at least some part of the edge adjacent to each other). When focusing or moving a container in a specified direction the center of the current focused container decides where to look for an adjacent output. So if e.g. an output has two adjacent outputs to the right and a "focus right" command is issued then it's the placement of the currently focused container that decides which output actually gets focused. Also, if an output has at least one output adjacent in some direction but the entire edge is not covered (ie. it has "holes" with no outputs), then the algorithm will choose the output that is closest to the currently focused container (this does not apply to seamless mouse, the pointer will just stop at the edge in that case).
* output: Fix code style.Libravatar S. Christoffer Eliesen2015-10-25
|
* sway/output: Create, move code from handlers.c here.Libravatar S. Christoffer Eliesen2015-10-25