| Commit message (Collapse) | Author | Age |
|\
| |
| | |
Implement floating_modifier and mouse operations for floating views
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
I discovered we have to send a click event when ending the move or
resize operation to make xwayland's requests work correctly.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Also does a few other related things:
* Now uses enum wlr_edges instead of our own enum resize_edge
* Now uses wlr_xcursor_get_resize_name and removes our own
find_resize_edge_name
* Renames drag to move for consistency
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When interactively resizing some views (eg. Nautilus), new transactions
are added to the queue faster than the client can process them.
Previously, we would wait for the entire queue to be ready before
applying any of them, but in this case the transactions would time out,
giving the client choppy performance.
This changes the queue handling so it applies the transactions up to the
first waiting transaction, without waiting for the entire queue to be
ready.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
This implements the following:
* `floating_modifier` configuration directive
* Drag a floating window by its title bar
* Hold mod + drag a floating window from anywhere
* Resize a floating view by dragging the border
* Resize a floating view by holding mod and right clicking anywhere on
the view
* Resize a floating view and keep aspect ratio by holding shift while
resizing using either method
* Mouse cursor turns into resize when hovering floating border or corner
|
|\
| |
| | |
Reset outputs on reload
|
|/ |
|
|\
| |
| | |
Implement force_display_urgency_hint
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
The directive sets the timeout before an urgent view becomes normal
again after switching to it from another workspace.
Also:
* When an xwayland surface removes the urgent hint while the timer is
active, we now ignore the request. This happens as soon as the view
receives focus, so it was effectively making the timer pointless.
* The timeout is now only applied when switching to it from another
workspace.
|
|\
| |
| | |
Fix output wildcard handling
|
|/ |
|
|\
| |
| | |
swaybar: Fix scroll handling on workspace buttons
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As well as ignoring scroll events on status elements when click_events
is enabled.
Previously, using the scroll wheel on a workspace button would switch to
that workspace instead of scrolling through them. Clicks and scrolling
on status elements would always be processed by swaybar, too. So in case
you were using scrolling as volume control on a status item, swaybar
would additionally scroll through your workspaces.
|
|\ \
| | |
| | | |
Fix pointer events for overlapping floating views
|
|/ /
| |
| |
| | |
Fixes #2315.
|
|\ \
| |/
|/| |
Update for swaywm/wlroots#1148
|
| |\
| |/
|/| |
|
|\ \
| | |
| | | |
Implement assign to output
|
| | |
| | |
| | |
| | | |
Eg. assign [class="Firefox"] output foo
|
|\ \ \
| |/ /
|/| | |
Fix deferred command handling
|
| | | |
|
| |/
|/| |
|
|\ \
| | |
| | | |
Allow xwayland views to become urgent when on a non-visible workspace
|
| |\ \
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | | |
Implement focus output command
|
| | | | |
|
| | | | |
|
| | |/
| |/| |
|
|\ \ \
| | | |
| | | | |
Fix crash and render issues involving cursor_send_pointer_motion
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes #2303, as well as a crash.
To replicate the crash:
* Have multiple outputs
* In config: for_window [<criteria>] workspace foo
* Also in config: workspace foo output <left-output-name>
* Focus the right output, and ensure workspace foo doesn't exist
* Launch the app that triggers the criteria
When the view maps, it calls workspace_switch which calls
send_set_focus which calls cursor_send_pointer_motion which calls
transaction_commit_dirty. This call to transaction_commit_dirty is not
meant to happen at this time because the tree isn't guaranteed to be in
a consistent state, but I'm not sure how exactly this leads to the crash
or render issues.
In this case the transaction is already committed by the view
implementation's handle_map function. So the solution is to remove it
from cursor_send_pointer_motion and add it to the other functions in
cursor.c which call cursor_send_pointer_motion.
|
|\ \ \
| |/ /
|/| | |
Fix crash when moving workspace to output
|
|/ / |
|
|/
|
|
|
|
|
| |
This removes the urgency stuff from the commit handler and puts it in a
new set_hints handler instead. This allows the xwayland surface to
become urgent without having to commit (which doesn't happen if it's on
an non-visible workspace).
|