| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
This distinguishes the binding mode from the distinct config mode, as
well as removing mode_pango_markup from the config struct where it
should not be present.
|
| |
|
| |
|
|
|
|
|
| |
This adds an id property to the bar, which will be used to filter
barconfig_update events
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Sway sets a default status_command which runs date every second. This
patch removes this behaviour so the user can have a NULL status bar if
desired.
I had to swap swaybar's event_loop_poll and wl_display_flush so that it
would map the initial surface.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
and lines with subpixel hinting (if available).
|
|
|
|
|
|
|
| |
This was the source of numerous bugs, from hotplug events not being
received to segfaults because wl_display_roundtrip was making the
bar process unplug events while blocking in an iteration over all
outputs.
|
|
|
|
| |
Don't kill and respawn swaybars on hotplug.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes #1855.
|
|
|
|
|
|
|
|
|
|
|
| |
Uses 'visible' instead of 'focused', since we may scroll on a bar which
isn't the focused output.
We can't use "next_on_output" or "prev_on_output" to implement this,
because it only modify the focused output. So scrolling on an unfocused
output will affect the incorrect one.
We just use the "workspace name" command instead.
|
|
|
|
| |
They're pointless.
|
|
|
|
|
| |
This prevents very high CPU load when the status command dies,
and poll continuously awoken with POLLHUP.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Does not yet support i3bar json protocol
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This starts up the event loop and wayland display and shims out the
basic top level rendering concepts. Also includes some changes to
incorporate pango into the 1.x codebase properly.
|
| |
|
|
|
|
|
| |
i3 bar handles scroll events as button 4 and 5. An example use
case would be volume up/down.
|
| |
|
| |
|
|
|
|
| |
This reverts commit 8f4bc0a3741b63c64bb6059bb632e7584c595d14.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes child proccess killing, when status_command is a complex command
like "i3status | wrapper.sh".
Set the process group id of the child process by calling `setpgid` after
forking and before calling `exec`.
The process group ID will be set to the process ID of the forked
process. Processes spawned by this child process will also have this
group ID.
Send signals to the process group with `killpg`. This will send the
signal to all of the process group.
|