Wrap the project into a namespace for easy killing on WM reset about asusctltray HOT 7 CLOSED

Sure, I can implement instance checking fairly easily, but what do you mean by "namespace"? I don't suppose you're referring to Linux process namespaces because I can't see how those would be influenced by a window manager. If you'd like to give more info on that, we could try working out a solution.

from asusctltray.

So basically what I am talking is how there is other applications that keep put in the appindicator (trayicons) usually have like this namespace(linux process name) which when you use

pkill <appname>

the app (the appindicator) will shutoff, which is not the case for this project. It shows only one thing: "python3" or "python" (as the process name).

So in short it shalt have a process name.

from asusctltray.

So for example here is leftwm's example for how they kill the custom trayicon stuff on reload and then start them on the end of reload:

fairly they have two files, namely up and down

up: https://github.com/AethanFoot/leftwm-theme-dracula-rounded/blob/master/up

(they start processes with specific name like dunst, picom, polybar)

down: https://github.com/AethanFoot/leftwm-theme-dracula-rounded/blob/master/down

(they kill processes with specific name like dunst, picom, polybar)

while the asusctltray project just have its process ran as a python3 runtime, rather than having its own namespace.

from asusctltray.

Actually this might be quite easy, as i saw this: https://code.google.com/archive/p/procname/

from asusctltray.

Sorry for the late response! Sure, I can work something out for that, but I'm going to treat as a low priority issue because I feel like this is more cosmetic than anything (since changing the process name is basically hacking around the Linux process namespaces working correctly). I'll work on it in the next couple days and report back.

from asusctltray.

Alright

from asusctltray.