osama/dwmblocks
1
0
Fork 0
mirror of https://github.com/mintycube/dwmblocks.git synced 2024-10-18 05:05:50 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update README and config.h

Browse Source
This commit is contained in:
Utkarsh Verma 2022-01-16 22:49:08 +05:30
parent 0471144a2e
commit 589d320b2e
No known key found for this signature in database
GPG Key ID: 817656CF818EFCCC
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -44,7 +44,7 @@ What's even better is that you can externally trigger updation of any specific b
## Why `dwmblocks-async`?
Everything I have mentioned till now is offered by the vanilla `dwmblocks`, which is fine for most users. What sets `dwmblocks-async` apart from vanilla `dwmblocks` is the 'async' part. `dwmblocks` executes the commands of each blocks sequentially which means that the mail and date blocks, from above example, would be executed one after the other. This means that the date block won't update unless the mail block is done executing, or vice versa. This is bad for scenarios where one of the blocks takes seconds to execute, and is clearly visible when you first start `dwmblocks`.
This is where the `dwmblocks-async` steps in tells the computer to execute each block asynchronously or simultaneously.
This is where the async nature of `dwmblocks-async` steps in tells the computer to execute each block asynchronously or simultaneously.
## Installation

4
config.h
View File

@ -9,8 +9,8 @@ const Block blocks[] = {
BLOCK("sb-memory", 10, 20),
BLOCK("sb-loadavg", 5, 21),
BLOCK("sb-mic", 0, 26),
BLOCK("sb-record", 0, 27),
BLOCK("sb-volume", 0, 22),
BLOCK("sb-battery", 5, 23),
BLOCK("sb-date", 1, 24),
// BLOCK("sb-network", 5, 25),
BLOCK("sb-date", 1, 24)
};