| Age | Commit message (Collapse) | Author |
|---|
|
|
|
The tablet will override the position anyway.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Add clickfinger in touchpad config
* Change `clickfinger` to `click-method`
* Change `bottom_areas` to `button_areas`
* Change button_areas to button-areas
For consistency.
* Reorder click methods in error message
The most usual one comes first.
* default-config: Move click-method down
---------
Co-authored-by: Ivan Molodetskikh <yalterz@gmail.com>
|
|
|
|
This reverts commit 40cec34aa4a7f99ab12b30cba1a0ee83a706a413.
The Chromium issues are now fixed.
|
|
gamescope + Minecraft with NeoForge throws an error upon starting if
there are no frame callbacks, thus making it the first client that has a
problem. Also, apparently, Veloren disconnects from server with VSync
and no frame callbacks.
|
|
|
|
|
|
|
|
This reverts commit 348690afb637514a38ad53fd61bf5e0102e419d6.
Apparently this breaks input in Chromium: the input region won't resize
together with the window.
|
|
libc::close_range() is not available on musl, so do this workaround for
now.
|
|
|
|
Currently outputs aren't repositioned again after a mode change, which
can cause overlaps.
|
|
|
|
|
|
Doesn't hurt I guess.
|
|
* Implement wlr-screencopy
* Finish the implementation
Lots of changes, mainly to fix transform handling. Turns out, grim
expects transformed buffers and untransforms them by itself using info
from wl_output. This means that render helpers needed to learn how to
actually render transformed buffers.
Also, it meant that y_invert is no longer needed.
Next, moved the rendering to the Screencopy frame handler. Turns out,
copy() is more or less expected to return immediately, whereas
copy_with_damage() is expected to wait until the next VBlank. At least
that's the intent I parse reading the protocol.
Finally, brought the version from 3 down to 1, because
copy_with_damage() will need bigger changes. Grim still works, others
not really, mainly because they bind v3 unnecessarily, even if they
don't use the damage request.
---------
Co-authored-by: Ivan Molodetskikh <yalterz@gmail.com>
|
|
|
|
|
|
* Add dinit support
- Add --notify-fd cli flag for ready notifications
- Set dinit activation environment when "dinit" feature flag is enabled
* Make systemd and dinit environment activation additive
* Use NOTIFY_FD env variable instead of --notify-fd cli flag for sending ready notifications
* Format with rustfmt
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Work around an integer overflow.
See: https://github.com/YaLTeR/niri/issues/239
|
|
|
|
|
|
|
|
|
|
400 is for width not height.
|
|
|
|
With inertia in place it's ready for this.
|
|
Values and implementation are heavily inspired by AdwSwipeTracker.
|
|
It can currently happen that the estimated VBlank timer fires right
before a real VBlank, which can cause some sequence collisions, which
might cause frame callbacks to never be sent. To prevent this, just
track the frame callback sequence fully separately. There isn't really
any harm in this, and if we accidentally increment it more frequently
than necessary then nothing terrible will happen.
|
|
* add dev dependencies to flake
* parse only one default-column-width
* require exactly one action per bind, and unique keys for binds
* use proper filename for config errors if possible
* fix duplicate keybinds after invalid action, lose some sanity
|
|
Before this commit:
- niri queues frame
- successful VBlank happens, sequence is bumped, frame callbacks are
sent
- niri receives commit, redraws, queues next frame, tries to send frame
callbacks, but there wasn't a new VBlank yet, so the sequence is old,
and frame callbacks aren't sent
- frame callbacks are sent only next VBlank
|
|
|
