| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When there are outputs with mixed scales, it was possible for swaybar to
alter `block->separator_block_width` for an output with a higher scale,
and use the changed value for a lower scale output. This caused there to
be larger than normal separation between blocks on the lower scale
outputs. The issue is more obvious the larger the scale difference
between the highest scale output and the lowest scale output.
This fixes the issue by using a local variable that is originally set to
`block->separator_block_width` for rendering, but if it needs to be
increased, the local variable is the only thing touched.
|
| |
|
|
|
|
|
| |
When `block->urgent` is set, use the urgent colors. This matches i3bar's
behavior. Previously, swaybar just ignored the property.
This also adds in rendering for right borders, which was missing.
|
| |
|
|
| |
Compatibility with i3 commit 161db6f17d734ac9deb0a20e81b78d4b2a92ce68.
|
| |
|
|
|
|
|
|
|
| |
Adds the bar subcommand `gaps <amount>|<horizontal> <vertical>|<top>
<right> <bottom> <left>` to set gaps for swaybar. Due to restrictions on
margins for a layer_surface, only the sides that are anchored to an edge
of the screen can have gaps. Since there is support for per-side outer
gaps for workspaces, those should be able to be used instead for the
last side.
|
| | |
|
| |
|
|
|
| |
This makes it congruent with its visual appearance, making it easier to
reason about.
|
| | |
|
| |
|
|
|
|
|
|
| |
Previously, when the bar was hidden, the height would be set to 0.
This meant that if the bar was empty upon reshow, it would not render
since the height was still 0, which made it seem there was a problem.
Now, the height is not reset, but the width is, to indicate upon reshow
that the layer surface needed reconfiguring.
|
| |
|
|
|
|
|
|
|
| |
As well as adding the hidden_state property to the bar config struct,
this commit handles barconfig_update events when the mode or
hidden_state changes, and uses a new function determine_bar_visibility
to hide or show the bar as required, using, respectively,
destroy_layer_surface, which is also newly added, and add_layer_surface,
which has been changed to allow dynamically adding the surface.
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
This now correctly handles an incoming json infinite array by shifting
most of the heavy listing to the json-c parser, as well as sending
multiple statuses at once. It also removes the struct
i3bar_protocol_state and moves its members into the status_line struct,
allowing the same buffer to be used for both protocols.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This prevents blocks from being destroyed before their hotspots are destroyed,
in case it is used for a pending click event that fires between the bar
receiving a new status, which destroys the block, and the bar rendering the new
status, which destroys the hotspot; this problem can be easily produced by
scrolling on a block that immediately causes a new status to be sent, with
multiple outputs
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This does the following:
* Adds a baseline argument to get_text_size (the baseline is the
distance from the top of the texture to the baseline).
* Stores the baseline in the container when calculating the title
height.
* Takes the baseline into account when calculating the config's max font
height.
* When rendering, pads the textures according to the baseline so they
line up.
|
| |
|
| |
Same as #2571 but for 1.0.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
When turning off displays via DPMS, swaybar and swaybg still tried to
render, but did not get a valid buffer, causing them to crash.
|
| | |
|
| | |
|
| |
|
|
|
| |
Makes swaybar respect the user's pango_markup configuration in the
workspace buttons and binding mode indicator.
|
| |
|
|
|
|
|
| |
Fixes #1796
Also rearranged this code to more closely mirror the similar code above
so future discrepancies are easier to spot.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
If strip_workspace_numbers option is enabled, we must preserve the right
workspace name for hotspot.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Does not yet support i3bar json protocol
|
| | |
|
| |
|
|
| |
This is an i3-gaps feature we support
|
| | |
|
Ian Fan
Brian Ashworth
Hristo Venev
Connor E
Geoff Greer
emersion
Ryan Dwyer
Jason
minus
Peter Rice
Drew DeVault
db