Hi everyone, I would like to change the way awesome handles the systray, and I am writing this email to the list to get mainly two questions answered:
1. Is there a reason why the change I am proposing is not quite as simple as I imagine it will be. 2. Will a patch with these set of changes get pushed to master, assuming it is correct (I guess only JD can answer this one). Currently awesome calls the systray_init and the systray_cleanup functions inside awesome.c. This means that awesome's systray gets created even if you do not have a widget for it (or even a wibox for that mater). This gives rise to two different sets of problems: a) If you do not want a systray at all, you won't create the widget. Then you naively start an application, say skype for example, and when you close it the window will disappear from the tag and the tasklist, but it is in fact still running since its hidden in the systray somewhere (even though you don't see it). b) If you want to use ANOTHER systray, then awesome will randomly still some (or all) the systray icons from you, it doesn't matter if you start the "other" systray before or after awesome. This is my problem, since I recently decided to use gnome-panel in my netbook. Now, at least at first sight it seems all of these issues would disappear if the systray_init/systray_cleanup functions where called when the systray widget was created/destroyed instead of calling them when awesome stars/stops. Your input is appreciated. Best, -- Alex -- To unsubscribe, send mail to [email protected].
