Consolatis
Consolatis
Yes, actions in specific require the `name` attribute to come first. I am also not that happy about it and we should figure out how to make the argument ordering...
You could archive something similar with [wlrctl](https://git.sr.ht/~brocellous/wlrctl). Although I don't see how you could move the cursor back to its original position. Writing some char and deleting it again should...
This use-case might be better served with some `MoveToRegion` action.
> `SnapToRegion`? It makes window snapped and always resizes. Right, a `MoveToRegion` action would only take the x and y values of the region and move the window there.
A hacky workaround would be to use https://labwc.github.io/labwc-config.5.html#margin or spawn some random exclusive-zone layershell client on each of the edges. That should at least prevent maximized / edge+region snapped windows...
> is there any configuration I need to make to labwc to enable virtual input devices? Not that I am aware of. Labwc should support the `zwp_virtual_keyboard_v1`, `zwp_input_method_v2` and `zwp_text_input_v3`...
Just a small nitpick: using `wlr/workspaces` feels wrong, its the official wayland protocol for workspaces rather than a wlroots one.
I'd just `s/wlr/ext/g` and call it a day.
CC @tokyo4j regarding potentially missing input-method integrations
labwc / wlroots are completely happy to run with no outputs connected. You wouldn't want labwc to terminate just because you physically disconnected your monitor either I assume. But I...