Piotr Miller

You may have a better idea. My solution only supports symbolic output names (like `eDP-1`). I list them by the sway IPC, then list `Gdk.Monitor` instances. By comparing `x` and...

To list outputs on other compositors, you'd need to talk to wlroots, or just parse `wlr-randr` output.

Of course. I didn't care about it much, as the shell is primarily aimed at sway. Finally I won't avoid doing the same.

While working on the Swaync panel module, I realized, that the output selection is not really essential to me, since the client will be opened on icon click. In most...

No hurry, if it comes to integration with the shell. It's absolutely usable as is, and looks great.

For my use case I just attached `swaync-client -t` to a panel icon, so the window opens where I want it to. No major problem. 

I think it would be good to show both batteries separately. The problem is that I have no hardware to give it a try. It would be better to write...

> The sensors_battery function [We already use it](https://github.com/nwg-piotr/nwg-panel/blob/ebd418108c92c849321918ac71c2007bd761804d/nwg_panel/tools.py#L487), but it returns a single value on my machine: ```text [piotr@msi ~]$ python Python 3.10.5 (main, Jun 6 2022, 18:49:26) [GCC 12.1.0]...

Do you have 2 batteries in the output of `upower -e | grep devices/battery`?

Yes, but nwg-panel already uses `upower` as an alternative method. We would only need to add some settings to force use of it, and to make use of multiple results.