pgrondek/polybar-dwm
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Cleanup Changelog

Browse Source
This commit is contained in:
patrick96 2022-02-22 18:29:56 +01:00 committed by Patrick Ziegler
parent f1490a13ca
commit eb535998da
1 changed files with 183 additions and 107 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

290
CHANGELOG.md
View File

@ -15,17 +15,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
configuration files, therefore if you want to use it in a value as a literal configuration files, therefore if you want to use it in a value as a literal
backslash, you need to escape it with the backslash escape character. The backslash, you need to escape it with the backslash escape character. The
parser logs an error if any unescaped backslashes are found in a value. This parser logs an error if any unescaped backslashes are found in a value. This
affects you only if you are using two consecutive backslashes in a value, affects you only if you are using two consecutive backslashes in a config
which will now be interpreted as a single literal backslash. value, which will now be interpreted as a single literal backslash.
[`#2354`](https://github.com/polybar/polybar/issues/2354) ([`#2354`](https://github.com/polybar/polybar/issues/2354))
- We rewrote our tag parser. This shouldn't break anything, if you experience - We rewrote our formatting tag parser. This shouldn't break anything, if you
any problems, please let us know. experience any problems, please let us know. The new parser now gives errors
The new parser now gives errors for certain invalid tags where the old parser for certain invalid tags where the old parser would just silently ignore them.
would just silently ignore them. Adding extra text to the end of a valid tag Adding extra text to the end of a valid tag now produces an error. For example,
now produces an error. For example, tags like `%{T-a}`, `%{T2abc}`, `%{rfoo}`, tags like `%{T-a}`, `%{T2abc}`, `%{rfoo}`, and others will now start producing
and others will now start producing errors. errors. This does not affect you unless you are producing your own invalid
This does not affect you unless you are producing your own formatting tags formatting tags (for example in a script).
(for example in a script) and you are using one of these invalid tags.
- For security reasons, the named pipe at `/tmp/polybar_mqueue.<PID>` had its - For security reasons, the named pipe at `/tmp/polybar_mqueue.<PID>` had its
permission bits changed from `666` to `600` to prevent sending ipc messages permission bits changed from `666` to `600` to prevent sending ipc messages
to polybar processes running under a different user. to polybar processes running under a different user.
@ -51,18 +50,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
targets can still be enabled explicitly. targets can still be enabled explicitly.
- The documentation can no longer be built by directly configuring the `doc` - The documentation can no longer be built by directly configuring the `doc`
directory. directory.
- The sample config file is now placed in the `generated-sources` folder inside
whatever folder you invoked `cmake` from instead of in the root folder of the
repository.
- The `POLYBAR_FLAGS` cmake variable can be used to pass extra C++ compiler flags. - The `POLYBAR_FLAGS` cmake variable can be used to pass extra C++ compiler flags.
- The sample config file has been removed. - The sample config file has been removed.
- Polybar now ships a default config that is installed to - Polybar now ships a default config that is installed to
`/etc/polybar/config.ini`, it lives in `doc/config.ini`. `/etc/polybar/config.ini`, it lives in `doc/config.ini`.
It will also be placed in the `examples` directory in the documentation folder. It will also be placed in the `examples` directory in the documentation folder.
[`#2405`](https://github.com/polybar/polybar/issues/2405) ([`#2405`](https://github.com/polybar/polybar/issues/2405))
- The `userconfig` target has been removed, you can no longer use `make - The `userconfig` target has been removed, you can no longer use `make
userconfig`. As an alternative, you can copy the default config from userconfig`. As an alternative, you can copy the default config from
`/etc/polybar/config.ini`. `/etc/polybar/config.ini`.
- The `DEBUG_SHADED` cmake variable and its associated functionality has been
removed.
### Deprecated ### Deprecated
- `[settings]`: `throttle-output` and `throttle-output-for` have been removed. - `[settings]`: `throttle-output` and `throttle-output-for` have been removed.
@ -77,156 +75,234 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- `polybar-msg hook` is deprecated in favor of using the hook action. - `polybar-msg hook` is deprecated in favor of using the hook action.
`polybar-msg` will tell you the correct command to use. `polybar-msg` will tell you the correct command to use.
### Removed
- `DEBUG_SHADED` cmake variable and its associated functionality.
### Added ### Added
- `custom/script`: Add formatting for script failure (`format-fail`, `label-fail`) ([`#2588`](https://github.com/polybar/polybar/issues/2588))
- Support `px` and `pt` units everyhwere where before only a number of spaces - Support `px` and `pt` units everyhwere where before only a number of spaces
or pixels could be specified. or pixels could be specified.
([`#2578`](https://github.com/polybar/polybar/pull/2578)) ([`#2578`](https://github.com/polybar/polybar/pull/2578),
- Right and middle click events for alsa module. [`#1651`](https://github.com/polybar/polybar/issues/1651),
([`#2566`](https://github.com/polybar/polybar/issues/2566)) [`#951`](https://github.com/polybar/polybar/issues/951))
- `internal/network`: New token `%mac%` shows MAC address of selected interface - `internal/alsa`: Right and middle click settings.
([`#2568`](https://github.com/polybar/polybar/issues/2568)) ([`#2566`](https://github.com/polybar/polybar/issues/2566),
[`#2573`](https://github.com/polybar/polybar/pull/2573))
- `internal/network`:
- New token `%mac%` shows MAC address of selected interface
([`#2568`](https://github.com/polybar/polybar/issues/2568),
[`#2569`](https://github.com/polybar/polybar/pull/2569))
- New token `%netspeed%` that provides the total speed of the internet (up +
down speed)
([`#2590`](https://github.com/polybar/polybar/pull/2590),
[`#1083`](https://github.com/polybar/polybar/issues/1083))
- `speed-unit = B/s` can be used to customize how network speeds are
displayed.
([`#2068`](https://github.com/polybar/polybar/pull/2068))
- `interface-type` may be used in place of `interface` to automatically
select a network interface
([`#2025`](https://github.com/polybar/polybar/pull/2025),
[`#339`](https://github.com/polybar/polybar/issues/339))
- Polybar can now read config files from stdin: `polybar -c /dev/stdin`. - Polybar can now read config files from stdin: `polybar -c /dev/stdin`.
- `custom/script`: Implement `env-*` config option. ([`#2545`](https://github.com/polybar/polybar/pull/2545))
([`#2090`](https://github.com/polybar/polybar/issues/2090)) - `custom/script`:
- `drawtypes/ramp`: Add support for ramp weights. - Setting environment variables using `env-*` config option.
([`#1750`](https://github.com/polybar/polybar/issues/1750)) ([`#2090`](https://github.com/polybar/polybar/issues/2090),
[`#2512`](https://github.com/polybar/polybar/pull/2512))
- Add formatting for script failure (`format-fail`, `label-fail`)
([`#2588`](https://github.com/polybar/polybar/issues/2588),
[`#2596`](https://github.com/polybar/polybar/pull/2596))
- Support for ramp weights.
([`#1750`](https://github.com/polybar/polybar/issues/1750),
[`#2505`](https://github.com/polybar/polybar/pull/2505))
- `internal/memory`: New tokens `%used%`, `%free%`, `%total%`, `%swap_total%`, - `internal/memory`: New tokens `%used%`, `%free%`, `%total%`, `%swap_total%`,
`%swap_free%`, and `%swap_used%` that automatically switch between MiB and GiB `%swap_free%`, and `%swap_used%` that automatically switch between MiB and GiB
when below or above 1GiB. when below or above 1GiB.
([`#2472`](https://github.com/polybar/polybar/issues/2472)) ([`#2472`](https://github.com/polybar/polybar/issues/2472),
- Option to always show urgent windows in i3 module when `pin-workspace` is active [`#2488`](https://github.com/polybar/polybar/pull/2488))
([`#2374`](https://github.com/polybar/polybar/issues/2374)) - `internal/i3`: `show-urgent` option to always show urgent windows when
- `internal/xworkspaces`: `reverse-scroll` can be used to reverse the scroll `pin-workspace` is active
direction when cycling through desktops. ([`#2374`](https://github.com/polybar/polybar/issues/2374),
- The backslash escape character (\\). [`#2378`](https://github.com/polybar/polybar/pull/2378))
[`#2354`](https://github.com/polybar/polybar/issues/2354) - `internal/xworkspaces`:
- `reverse-scroll` can be used to reverse the scroll
direction when cycling through desktops.
([`#2365`](https://github.com/polybar/polybar/pull/2365))
- `%nwin%` can be used to display the number of open
windows per workspace
([`#604`](https://github.com/polybar/polybar/issues/604),
[`#2329`](https://github.com/polybar/polybar/pull/2329))
- Initial support for the backslash escape character (\\) in configs.
([`#2354`](https://github.com/polybar/polybar/issues/2354),
[`#2361`](https://github.com/polybar/polybar/pull/2361))
- Warn states for the cpu, memory, fs, and battery modules. - Warn states for the cpu, memory, fs, and battery modules.
([`#570`](https://github.com/polybar/polybar/issues/570), ([`#570`](https://github.com/polybar/polybar/issues/570),
[`#956`](https://github.com/polybar/polybar/issues/956), [`#956`](https://github.com/polybar/polybar/issues/956),
[`#1871`](https://github.com/polybar/polybar/issues/1871), [`#1871`](https://github.com/polybar/polybar/issues/1871),
[`#2141`](https://github.com/polybar/polybar/issues/2141)) [`#2141`](https://github.com/polybar/polybar/issues/2141),
[`#2199`](https://github.com/polybar/polybar/pull/2199))
- `internal/battery`: `format-low`, `label-low`, `animation-low`, `low-at = 10`. - `internal/battery`: `format-low`, `label-low`, `animation-low`, `low-at = 10`.
- `internal/cpu`: `format-warn`, `label-warn`, `warn-percentage = 80` - `internal/cpu`: `format-warn`, `label-warn`, `warn-percentage = 80`
- `internal/fs`: `format-warn`, `label-warn`, `warn-percentage = 90` - `internal/fs`: `format-warn`, `label-warn`, `warn-percentage = 90`
- `internal/memory`: `format-warn`, `label-warn`, `warn-percentage = 90` - `internal/memory`: `format-warn`, `label-warn`, `warn-percentage = 90`
- `radius` now affects the bar border as well - `radius` now affects the bar border as well
([`#1566`](https://github.com/polybar/polybar/issues/1566)) ([`#1566`](https://github.com/polybar/polybar/issues/1566),
[`#2359`](https://github.com/polybar/polybar/pull/2359))
- Per-corner radius with `radius-{bottom,top}-{left,right}` - Per-corner radius with `radius-{bottom,top}-{left,right}`
([`#2294`](https://github.com/polybar/polybar/issues/2294)) ([`#2294`](https://github.com/polybar/polybar/issues/2294),
- `internal/network`: `speed-unit = B/s` can be used to customize how network [`#2297`](https://github.com/polybar/polybar/pull/2297))
speeds are displayed. - `internal/xkeyboard`:
- `internal/xkeyboard`: `%variant%` can be used to parse the layout variant - `%variant%` token to display the keyboard layout variant
([`#316`](https://github.com/polybar/polybar/issues/316)) ([`#316`](https://github.com/polybar/polybar/issues/316),
[`#2163`](https://github.com/polybar/polybar/pull/2163))
- Allow matching of variants in `layout-icon`
([`#2414`](https://github.com/polybar/polybar/issues/2414),
[`#2521`](https://github.com/polybar/polybar/pull/2521))
- Config option to hide a certain module - Config option to hide a certain module
(`hidden = false`) (`hidden = false`)
([`#2108`](https://github.com/polybar/polybar/issues/2108)) ([`#2108`](https://github.com/polybar/polybar/issues/2108),
[`#2342`](https://github.com/polybar/polybar/pull/2342))
- Actions to control visibility of modules - Actions to control visibility of modules
(`module_toggle`, `module_show`, and `module_hide`) (`module_toggle`, `module_show`, and `module_hide`)
([`#2108`](https://github.com/polybar/polybar/issues/2108)) ([`#2108`](https://github.com/polybar/polybar/issues/2108),
- `internal/xworkspaces`: Make the urgent hint persistent [`#2426`](https://github.com/polybar/polybar/pull/2426))
([`#1081`](https://github.com/polybar/polybar/issues/1081)) - `internal/backlight`: `use-actual-brightness` option to use the
- `internal/network`: `interface-type` may be used in place of `interface` to `actual_brightness` file to get the brightness
automatically select a network interface ([`#2380`](https://github.com/polybar/polybar/pull/2380))
([`#2025`](https://github.com/polybar/polybar/pull/2025)) - `wm-restack = generic` option that lowers polybar to the bottom of the window stack.
- `internal/xworkspaces`: `%nwin%` can be used to display the number of open
windows per workspace
([`#604`](https://github.com/polybar/polybar/issues/604))
- `internal/backlight`: added `use-actual-brightness` option
- Added `wm-restack = generic` option that lowers polybar to the bottom of the stack.
Fixes the issue where the bar is being drawn on top of fullscreen windows in xmonad. Fixes the issue where the bar is being drawn on top of fullscreen windows in xmonad.
([`#2205`](https://github.com/polybar/polybar/issues/2205)) ([`#2205`](https://github.com/polybar/polybar/issues/2205),
- Added `occupied-scroll = true` option to bspwm module. [`#2404`](https://github.com/polybar/polybar/pull/2404))
Allows scrolling only through occupied desktops only. - `internal/bspwm`: `occupied-scroll = true` option allows scrolling through
([`#2427`](https://github.com/polybar/polybar/issues/2427)) occupied desktops only.
- `custom/ipc`: `send` action to send arbitrary strings to be displayed in the module. ([`#2427`](https://github.com/polybar/polybar/issues/2427),
([`#2455`](https://github.com/polybar/polybar/issues/2455)) [`#2428`](https://github.com/polybar/polybar/pull/2428))
- `custom/ipc`:
- `send` action to send arbitrary strings to be displayed in the module.
([`#2455`](https://github.com/polybar/polybar/issues/2455),
[`#2463`](https://github.com/polybar/polybar/pull/2463))
- `hook`, `next`, `prev`, `reset` actions to control the module through
actions instead of the deprecated hook messages
([`#2464`](https://github.com/polybar/polybar/issues/2464),
[`#2528`](https://github.com/polybar/polybar/pull/2528))
- Added `double-click-interval` setting to the bar section to control the time - Added `double-click-interval` setting to the bar section to control the time
interval in which a double-click is recognized. Defaults to 400 (ms) interval in which a double-click is recognized. Defaults to 400 (ms)
([`#1441`](https://github.com/polybar/polybar/issues/1441)) ([`#1441`](https://github.com/polybar/polybar/issues/1441),
- `internal/xkeyboard`: Allow configuring icons using variant [`#2510`](https://github.com/polybar/polybar/pull/2510))
([`#2414`](https://github.com/polybar/polybar/issues/2414))
- `custom/ipc`: Add `hook`, `next`, `prev`, `reset` actions to the ipc module
([`#2464`](https://github.com/polybar/polybar/issues/2464))
- Added a new `tray-foreground` setting to give hints to tray icons about what - Added a new `tray-foreground` setting to give hints to tray icons about what
color they should be. color they should be.
([#2235](https://github.com/polybar/polybar/issues/2235)) ([`#2235`](https://github.com/polybar/polybar/issues/2235),
[`#2552`](https://github.com/polybar/polybar/pull/2552))
- `polybar-msg`: - `polybar-msg`:
- For module actions, you can now also specify the module name, - For module actions, you can now also specify the module name,
action name, and optional data as separate arguments. action name, and optional data as separate arguments.
- Added man page ([`#2539`](https://github.com/polybar/polybar/pull/2539))
- `internal/network`: New token `%netspeed%` that provides the total speed of the internet (up + down speed) ([#2590](https://github.com/polybar/polybar/issues/2590)) - Added man page: `man 1 polybar-msg`
([`#2539`](https://github.com/polybar/polybar/pull/2539))
### Changed ### Changed
- Polybar now also reads `config.ini` when searching for config files. - Polybar now also reads `config.ini` when searching for config files.
([`#2323`](https://github.com/polybar/polybar/issues/2323)) ([`#2323`](https://github.com/polybar/polybar/issues/2323),
- Polybar additionally searches in `XDG_CONFIG_DIRS/polybar` (or [`#2324`](https://github.com/polybar/polybar/pull/2324))
`/etc/xdg/polybar` if it is not set) and `/etc/polybar` for config files - Polybar additionally searches in `XDG_CONFIG_DIRS/polybar/config.ini` (or
(only `config.ini`). `/etc/xdg/polybar/config.ini` if it is not set) and `/etc/polybar/config.ini` for config files.
([`#2016`](https://github.com/polybar/polybar/issues/2016)) ([`#2016`](https://github.com/polybar/polybar/issues/2016),
[`#2511`](https://github.com/polybar/polybar/pull/2511))
- We rewrote polybar's main event loop. This shouldn't change any behavior for - We rewrote polybar's main event loop. This shouldn't change any behavior for
the user, but be on the lookout for X events, click events, or ipc messages the user, but be on the lookout for X events, click events, or ipc messages
not arriving and the bar not shutting down/restarting properly and let us not arriving and the bar not shutting down/restarting properly and let us
know if you find any issues. know if you find any issues.
([`#2384`](https://github.com/polybar/polybar/pull/2384))
- Slight changes to the value ranges the different ramp levels are responsible - Slight changes to the value ranges the different ramp levels are responsible
for in the cpu, memory, fs, and battery modules. The first and last level are for in the cpu, memory, fs, and battery modules. The first level is used for
only used for everything at or below and at and above the edges of the value everything at and below the start of the value range and the last level for
range, respectively. The other levels are evenly distributed over the value everything at and above the end of the value range. The other levels are
range as before. evenly distributed over the value range as before. The value range is bounded
by the new warning thresholds.
([`#2199`](https://github.com/polybar/polybar/pull/2199))
- `custom/script`: `interval` now defaults to 0 if `tail = true` as per the - `custom/script`: `interval` now defaults to 0 if `tail = true` as per the
documentation. documentation.
- `internal/network`: ([`#2240`](https://github.com/polybar/polybar/pull/2240))
- Increased precision for upload and download speeds: 0 decimal places for - `internal/network`: Increased precision for upload and download speeds: 0 decimal places for
KB/s (as before), 1 for MB/s and 2 for GB/s. KB/s (as before), 1 for MB/s and 2 for GB/s.
([`#2054`](https://github.com/polybar/polybar/pull/2054))
- Clicks arriving in close succession, no longer get dropped. Before polybar - Clicks arriving in close succession, no longer get dropped. Before polybar
would drop any click that arrived within 5ms of the previous one. would drop any click that arrived within 5ms of the previous one.
([`#2510`](https://github.com/polybar/polybar/pull/2510))
- Increased the double click interval from 150ms to 400ms. - Increased the double click interval from 150ms to 400ms.
([`#2510`](https://github.com/polybar/polybar/pull/2510))
- Stop ignoring actions if they arrive while the previous one hasn't been processed yet. - Stop ignoring actions if they arrive while the previous one hasn't been processed yet.
([`#2469`](https://github.com/polybar/polybar/issues/2469)) ([`#2469`](https://github.com/polybar/polybar/issues/2469),
[`#2517`](https://github.com/polybar/polybar/pull/2517))
- Polybar can now be run without passing the bar name as argument given that - Polybar can now be run without passing the bar name as argument given that
the configuration file only defines one bar the configuration file only defines one bar
([`#2525`](https://github.com/polybar/polybar/issues/2525)) ([`#2525`](https://github.com/polybar/polybar/issues/2525),
[`#2526`](https://github.com/polybar/polybar/pull/2526))
- `include-directory` and `include-file` now support relative paths. The paths - `include-directory` and `include-file` now support relative paths. The paths
are relative to the folder of the file where those directives appear. are relative to the folder of the file where those directives appear.
([`#2523`](https://github.com/polybar/polybar/issues/2523)) ([`#2523`](https://github.com/polybar/polybar/issues/2523),
[`#2535`](https://github.com/polybar/polybar/issues/2535))
- `custom/ipc`: Empty output strings are no longer formatted. This prevents - `custom/ipc`: Empty output strings are no longer formatted. This prevents
extraneous spaces and separators from appearing in the bar when the output of extraneous spaces and separators from appearing in the bar when the output of
an ipc module is empty. an ipc module is empty.
([`#2549`](https://github.com/polybar/polybar/pull/2549))
### Fixed ### Fixed
- `custom/script`: Concurrency issues with fast-updating tailed scripts. - Broken positioning in Openbox when the bar is hidden and shown again
([`#1978`](https://github.com/polybar/polybar/issues/1978)) ([`#2021`](https://github.com/polybar/polybar/issues/2021),
- Trailing space after the layout label when indicators are empty and made sure right amount [`#2600`](https://github.com/polybar/polybar/pull/2600))
of spacing is added between the indicator labels, in the xkeyboard module. - Handling of action blocks that contain negative offsets
([`#2292`](https://github.com/polybar/polybar/issues/2292)) ([`#1814`](https://github.com/polybar/polybar/issues/1814),
[`#2601`](https://github.com/polybar/polybar/pull/2601))
- `polybar -m` used to show both physical outputs and RandR monitors, even if
the outputs were covered by monitors.
([`#2481`](https://github.com/polybar/polybar/issues/2481),
[`#2485`](https://github.com/polybar/polybar/pull/2485))
- Parser error if click command contained `}` - Parser error if click command contained `}`
([`#2040`](https://github.com/polybar/polybar/issues/2040)) ([`#2040`](https://github.com/polybar/polybar/issues/2040),
- Slight imprecision when calculating percentages. This caused the volume [`#2303`](https://github.com/polybar/polybar/pull/2303))
reported by alsa to be off by one. - Some modules stop updating when system time moves backwards.
([`#2399`](https://github.com/polybar/polybar/issues/2399)) ([`#857`](https://github.com/polybar/polybar/issues/857),
[`#1932`](https://github.com/polybar/polybar/issues/1932),
[`#2559`](https://github.com/polybar/polybar/pull/2559))
- `custom/script`: Concurrency issues with fast-updating tailed scripts.
([`#1978`](https://github.com/polybar/polybar/issues/1978),
[`#2518`](https://github.com/polybar/polybar/pull/2518))
- `internal/alsa`: Slight imprecision when calculating percentages. This caused the volume
reported to be off by one.
([`#2399`](https://github.com/polybar/polybar/issues/2399),
[`#2401`](https://github.com/polybar/polybar/pull/2401))
- `internal/backlight`: With amdgpu backlights, the brightness indicator was slightly behind. - `internal/backlight`: With amdgpu backlights, the brightness indicator was slightly behind.
([`#2367`](https://github.com/polybar/polybar/issues/2367)) ([`#2367`](https://github.com/polybar/polybar/issues/2367),
- Warning message regarding T@ in bspwm module [`#2380`](https://github.com/polybar/polybar/pull/2380))
([`#2371`](https://github.com/polybar/polybar/issues/2371)) - `internal/bspwm`: Warning message regarding T@
- `polybar -m` used to show both physical outputs and randr monitors, even if the outputs were covered by monitors. ([`#2371`](https://github.com/polybar/polybar/issues/2371),
([`#2481`](https://github.com/polybar/polybar/issues/2481)) [`#2439`](https://github.com/polybar/polybar/pull/2439))
- `internal/xkeyboard`: Trailing space after the layout label when indicators are empty and made sure right amount
of spacing is added between the indicator labels
([`#2292`](https://github.com/polybar/polybar/issues/2292),
[`#2306`](https://github.com/polybar/polybar/pull/2306))
- `internal/xworkspaces`: - `internal/xworkspaces`:
- Broken scroll-wrapping and order of workspaces when scrolling - Broken scroll-wrapping and order of workspaces when scrolling
([`#2491`](https://github.com/polybar/polybar/issues/2491)) ([`#2491`](https://github.com/polybar/polybar/issues/2491),
[`#2492`](https://github.com/polybar/polybar/pull/2492))
- Module would error if WM was not full started up. - Module would error if WM was not full started up.
([`#1915`](https://github.com/polybar/polybar/issues/1915)) ([`#1915`](https://github.com/polybar/polybar/issues/1915),
[`#2429`](https://github.com/polybar/polybar/pull/2429))
- Make the urgent hint persistent
([`#1081`](https://github.com/polybar/polybar/issues/1081),
[`#2340`](https://github.com/polybar/polybar/pull/2340))
- Crash when the WM sets -1 for `_NET_WM_DESKTOP`
([`#2352`](https://github.com/polybar/polybar/issues/2352),
[`#2353`](https://github.com/polybar/polybar/issues/2353))
- `internal/network`: The module now properly supports 'altnames' for - `internal/network`: The module now properly supports 'altnames' for
interfaces. interfaces.
([`#2540`](https://github.com/polybar/polybar/pull/2540))
- `internal/battery`: More accurate battery state - `internal/battery`: More accurate battery state
([`#2563`](https://github.com/polybar/polybar/issues/2563)) ([`#2563`](https://github.com/polybar/polybar/issues/2563),
- Some modules stop updating when system time moves backwards. ([`#857`](https://github.com/polybar/polybar/issues/857), [`#1932`](https://github.com/polybar/polybar/issues/1932)) [`#2556`](https://github.com/polybar/polybar/pull/2556))
- Broken positioning in Openbox when the bar is hidden and shown again - Offset tag does not respect current background color
([`#2021`](https://github.com/polybar/polybar/issues/2021)) ([`#2578`](https://github.com/polybar/polybar/pull/2578),
- Handling of action blocks that contain negative offsets [`#1700`](https://github.com/polybar/polybar/issues/1700))
([`#1814`](https://github.com/polybar/polybar/issues/1814)) - Crash when negative margin or padding was specified
([`#2578`](https://github.com/polybar/polybar/pull/2578),
[`#1265`](https://github.com/polybar/polybar/issues/1265))
## [3.5.7] - 2021-09-21 ## [3.5.7] - 2021-09-21
### Fixed ### Fixed