can't use BLOCK_BUTTON up to 10 about dwmblocks-async HOT 3 CLOSED

I am a bit unfamiliar ever since I had a last look at the code itself. But I'm gonna make a wild guess and say that this is expected.

iirc the buttons are handled by sending signals in between dwm and dwmblocks. There are so many signals that these two could use so maybe that's the reason.

Maybe checkout my patch0 that makes dwm handle this internally so these signals in between are avoided and the buttons are directly handled.

from dwmblocks-async.

Hi there, sorry for taking so long. This is definitely a dwmblocks-async bug. dwm actually allows you to have up to 256 click actions for a block.

@explosion-mental As I think you might be interested, here are how clicks are handled in dwm and dwmblocks:

• dwm: https://github.com/bakkeby/dwm-flexipatch/blob/master/patch/bar_dwmblocks.c#L39
• dwmblocks-async: https://github.com/UtkarshVerma/dwmblocks-async/blob/main/main.c#L204

This issue arose because I'm simply adding the value received from the signal and adding it to ASCII of '0'. This works fine for characters 0-9, but we get other ASCII characters up ahead instead of numbers.

I will be pushing changes to fix this behaviour.

from dwmblocks-async.

This should be fixed now, but feel free to reopen in case there are any issues.

from dwmblocks-async.