aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #49 from guidocella/layer-shellDevin J. Pohly2020-12-244-13/+771
|\ | | | | Layer shell
| * extract function and comment itGuido Cella2020-09-111-11/+18
| |
| * remove bracesGuido Cella2020-09-111-2/+1
| |
| * fix multi monitors even moreGuido Cella2020-09-111-6/+15
| | | | | | | | | | | | | | | | | | | | When a monitor is created or removed, the geometries of the old ones must be updated. This is also more efficient than before since we calculate the monitor geometries only when creating and destroying monitors. arrangelayers() is needed to recalculate m->w. arrange() is so clients don't move to the left monitor when plugging or unplugging monitors (clients keep the same coordinates but the field below them changes).
| * simplifyGuido Cella2020-09-101-1/+1
| |
| * fix multi monitors furtherGuido Cella2020-09-091-3/+1
| | | | | | | | | | Fix layer surfaces without an exculsive area by using the right x and y for the current monitor (by Stivvo).
| * remove unneeded lineGuido Cella2020-09-081-1/+0
| | | | | | | | | | | | | | The bug was caused by usable_area's x and y not being set in arrangelayers. For example if on a 2nd HD monitor, x should be 1920 while the first one ends at 1919. So I don't see why m->m should be recalculated after creating the monitor.
| * try to fix againGuido Cella2020-09-081-4/+1
| | | | | | | | Calculate x and y of usable_area, not just width and heigth.
| * fix multi monitorsGuido Cella2020-09-081-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you don't recalculate the monitor's geometry before arranging, clients get arranged in the first monitor. I don't understand why this fixes the bug since tile() uses m->w rather than m->m, nor why it needs to be recalculated after creating the monitor but sway does it too. Although not necessary to fix the bug I also made arrangelayer() do like sway again and recalculate usable_area instead of reusing m->m, since m->m seems to be incorrect until it gets recalculated shortly after in arrange(), so I suspect that leaving usable_area = m->m will cause issues under certain circumstances. Someone with a multi-monitor setup or better knowledge of Wayland may be able to figure out the cause of the bug. For now, this makes layer shell work.
| * remove variableGuido Cella2020-09-061-4/+3
| |
| * use size_t for lengthsGuido Cella2020-09-051-4/+4
| |
| * rename variable and merge 2 linesGuido Cella2020-09-051-3/+2
| |
| * simplifyGuido Cella2020-09-051-10/+4
| |
| * use unsigned int for loop indexesGuido Cella2020-09-041-3/+3
| |
| * Don't let overlays lose focusGuido Cella2020-09-041-2/+20
| | | | | | | | | | if you open a new window while an overlay is mapped, the overlay should stay focused
| * fix restoring pointer focusGuido Cella2020-09-041-1/+6
| | | | | | | | | | I don't know why I thought it was working before. Maybe I should go do something else.
| * improve code styleGuido Cella2020-09-041-4/+4
| |
| * remove commentGuido Cella2020-09-041-1/+1
| | | | | | | | | | I don't know why it wasn't working before but now it does ¯\(ツ)/¯ (it wasn't caused by the just removed code either)
| * remove mysterious codeGuido Cella2020-09-041-7/+0
| | | | | | | | | | Why would a surface that's not keyboard interactive get focused? Let's remove this for now and see if issues arise.
| * focus the previous client in the similar code tooGuido Cella2020-09-041-2/+1
| |
| * refocus old clientGuido Cella2020-09-041-3/+1
| | | | | | | | | | | | When a layer surface is destroyed focus should be returned to the last client. Luckily if there are multiple overlays the previous overlay still gets focused.
| * fix alhpabetical orderGuido Cella2020-09-041-8/+8
| |
| * simplify focus leave conditionGuido Cella2020-09-041-7/+2
| |
| * reuse motionnotify()Guido Cella2020-09-041-10/+8
| |
| * enable pointer on layer surfacesGuido Cella2020-09-041-5/+49
| |
| * more TODOsGuido Cella2020-09-031-2/+3
| |
| * fix focus leave conditionGuido Cella2020-09-031-3/+4
| | | | | | | | needs refactoring and testing
| * send pressed keys to topmost layer surfaceGuido Cella2020-09-031-2/+3
| |
| * update READMEGuido Cella2020-08-291-1/+0
| |
| * remove blank lineGuido Cella2020-08-291-1/+0
| |
| * don't handle failed callocGuido Cella2020-08-291-2/+0
| | | | | | | | be consistent with the rest of the code
| * order variables more how like they are initializedGuido Cella2020-08-291-1/+1
| |
| * simplify make cleanGuido Cella2020-08-281-1/+1
| |
| * Reuse render() and struct timespec *nowGuido Cella2020-08-281-36/+14
| |
| * reuse m->mGuido Cella2020-08-271-4/+1
| |
| * remove commentGuido Cella2020-08-271-2/+0
| | | | | | | | | | wlr_output_layout_get_box internally calls wlr_output_effective_resolution
| * set a monitor geometry only when creating itGuido Cella2020-08-271-3/+4
| | | | | | | | Lets layers with an exclusive area shrink the usable area
| * render in the same order as swayGuido Cella2020-08-271-2/+2
| |
| * update make cleanGuido Cella2020-08-261-1/+1
| |
| * correct variable nameGuido Cella2020-08-261-1/+1
| |
| * rename functions tooGuido Cella2020-08-261-19/+19
| |
| * remove extra spaceGuido Cella2020-08-261-1/+1
| |
| * render layer surfacesGuido Cella2020-08-261-0/+43
| |
| * improve namingGuido Cella2020-08-261-62/+63
| | | | | | | | | | | | | | rename Layer to LayerSurface; layer should refer to overlay, top, bottom or background LayerSurface variables are always called layersurface wlr_layer_surface_v1 variables are always called wlr_layer_surface
| * layer shell initial attemptGuido Cella2020-08-243-2/+688
| |
* | use the install command to installDevin J. Pohly2020-12-241-3/+1
| |
* | Merge pull request #65 from Keating950/masterDevin J. Pohly2020-12-242-0/+8
|\ \ | | | | | | Add install target to Makefile
| * | add install target to Makefile and corresponding prefix variable to config.mkKeating9502020-11-222-0/+8
| |/
* | Merge pull request #56 from oyren/readme_logDevin J. Pohly2020-12-241-6/+0
|\ \ | | | | | | remove log flags from readme
| * | remove log flags from readmeOyren2020-09-141-6/+0
| |/ | | | | | | The following commit has removed the logs but they are still in the readme. https://github.com/djpohly/dwl/commit/3b1992ca91b9a468019165c985263f5b1cc78c2c