kriansa / wmcompanion Goto Github PK

Hi, so I was thinking about something, to continue the conversation from reddit where you were interested in feedback. How about this framework have two modular components, one that publishes events on dbus and the other that handles the actions part, here would be a rough workflow:

M1:

1. collect all events from udev etc (also dbus itself?)

2. republish them on your own bus

M2:

1. Python API to directly subscribe to your events. (Or to dbus events)

2. affect stuff like polybar , notify etc

You're already doing everything except (2) of M1. I think having a (2) would appeal a lot to what is already the target audience, people who want to minimize stuff that runs on their computer.

Eg. I use a heavily modified fork of qmpanel where I have added some dbus listening and would write my own cpp to do stuff by listening to your bus.

Dbus would allow me to do things in- process and in general is a more standard approach imho.

Thanks for this module. Is there an event that can detect when a monitor gets attached or detched?

Greetings, so, I have this snippet of code here:

from wmcompanion.events.power import PowerActions

when I run it, it seems that WMCompanion runs into an error whilst trying to connect with the "/sys/class/power_supply/BAT0/capacity" file, necessary for PowerActions to work. This is because many systems actually store this file at "/sys/class/power_supply/BAT1/capacity" or "/sys/class/power_supply/BAT2/capacity" and so on and so forth. This same issue occured in bpytop and was fixed via a merge. I can attempt to fix this via a merge as well if needed. (this is the fix in bpytop -> lwhsu/bpytop@6643dc2).

Regards,
Trayambak.