62529e251d
Merge pull request #49 from guidocella/layer-shell
...
Layer shell
2020-12-24 20:24:14 -05:00
41d7fdbd60
use the install command to install
2020-12-24 19:07:38 -05:00
8dd99d2a10
Merge pull request #65 from Keating950/master
...
Add install target to Makefile
2020-12-24 19:07:08 -05:00
e0f11abd13
Merge pull request #56 from oyren/readme_log
...
remove log flags from readme
2020-12-24 18:57:55 -05:00
b6a3891ce6
Merge pull request #62 from Java-boi/master
...
Added basic tap-to-click for touchpad users
2020-12-24 18:55:06 -05:00
a42613db9d
Merge pull request #66 from richardipsum/master
...
fix undeclared WLR_KEY_PRESSED
2020-12-24 14:28:04 -06:00
67896e9d8b
fix undeclared WLR_KEY_PRESSED
2020-11-23 16:58:43 +00:00
9578816487
add install target to Makefile and corresponding prefix variable to config.mk
2020-11-22 12:58:49 -05:00
7ad14a9660
Added support for natural scrolling
2020-10-17 16:18:44 +02:00
598516d808
Added basic tap-to-click for touchpad users
2020-10-17 13:52:53 +02:00
a2e5c25e26
remove log flags from readme
...
The following commit has removed the logs but they are still in the readme.
3b1992ca91
2020-09-14 20:45:39 +02:00
0bb25a73ec
extract function and comment it
2020-09-11 14:52:59 +02:00
e4d58c39e0
remove braces
2020-09-11 13:15:31 +02:00
fbd905155a
fix multi monitors even more
...
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).
2020-09-11 13:09:18 +02:00
8f0ce672d3
simplify
2020-09-10 06:01:18 +02:00
143dce094c
fix multi monitors further
...
Fix layer surfaces without an exculsive area by using the right x and y
for the current monitor (by Stivvo).
2020-09-09 17:13:30 +02:00
62250661cf
remove unneeded line
...
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.
2020-09-08 13:36:46 +02:00
68412d8957
try to fix again
...
Calculate x and y of usable_area, not just width and heigth.
2020-09-08 12:49:05 +02:00
69847872bb
fix multi monitors
...
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.
2020-09-08 10:28:29 +02:00
79f3bbaf38
remove variable
2020-09-06 19:59:58 +02:00
52a4d3a1e5
use size_t for lengths
2020-09-05 18:29:39 +02:00
9743778d09
rename variable and merge 2 lines
2020-09-05 14:15:03 +02:00
6b25e7ef27
simplify
2020-09-05 06:58:54 +02:00
8ee0200877
use unsigned int for loop indexes
2020-09-04 21:36:43 +02:00
ae798c694a
Don't let overlays lose focus
...
if you open a new window while an overlay is mapped, the overlay should
stay focused
2020-09-04 21:35:48 +02:00
8de18f9bb4
fix restoring pointer focus
...
I don't know why I thought it was working before. Maybe I should go do
something else.
2020-09-04 21:14:02 +02:00
71572521e9
improve code style
2020-09-04 18:45:30 +02:00
9308a90d11
remove comment
...
I don't know why it wasn't working before but now it does ¯\(ツ)/¯
(it wasn't caused by the just removed code either)
2020-09-04 18:04:20 +02:00
8e81c90f31
remove mysterious code
...
Why would a surface that's not keyboard interactive get focused? Let's
remove this for now and see if issues arise.
2020-09-04 17:38:37 +02:00
2d84c74657
focus the previous client in the similar code too
2020-09-04 17:38:04 +02:00
068352e888
refocus old client
...
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.
2020-09-04 17:21:48 +02:00
4341deae8f
fix alhpabetical order
2020-09-04 17:01:34 +02:00
5dc9460044
simplify focus leave condition
2020-09-04 16:42:14 +02:00
35b93669f1
reuse motionnotify()
2020-09-04 15:35:04 +02:00
d98ca07a64
enable pointer on layer surfaces
2020-09-04 07:42:51 +02:00
b26ede4727
more TODOs
2020-09-03 18:59:27 +02:00
4017a27b67
fix focus leave condition
...
needs refactoring and testing
2020-09-03 18:58:27 +02:00
b4d9a8662f
send pressed keys to topmost layer surface
2020-09-03 18:34:41 +02:00
d74d404026
update README
2020-08-29 08:47:28 +02:00
5d4eadeb8e
remove blank line
2020-08-29 08:42:17 +02:00
3203d1bafd
don't handle failed calloc
...
be consistent with the rest of the code
2020-08-29 08:41:51 +02:00
ddd3c2ad7e
order variables more how like they are initialized
2020-08-29 07:42:47 +02:00
b237ea0e45
simplify make clean
2020-08-28 15:17:38 +02:00
2c08d0b421
Reuse render() and struct timespec *now
2020-08-28 09:00:03 +02:00
03c020f058
reuse m->m
2020-08-27 06:45:26 +02:00
1473d03293
remove comment
...
wlr_output_layout_get_box internally calls
wlr_output_effective_resolution
2020-08-27 06:04:57 +02:00
c9f92bdd0e
set a monitor geometry only when creating it
...
Lets layers with an exclusive area shrink the usable area
2020-08-27 05:22:27 +02:00
b8a6d3e86a
render in the same order as sway
2020-08-27 05:03:01 +02:00
d61658bdd7
update make clean
2020-08-26 21:05:44 +02:00
e13d193346
correct variable name
2020-08-26 19:52:03 +02:00
Devin J. Pohly
Richard Ipsum
Keating950
will
Oyren
Guido Cella