Emmanuel Lepage Vallée
Emmanuel Lepage Vallée
Or at least move them to the current screen, but it doesn't make a lot of sense.
Like the tasklist one Example usage: - Client counter - Extra state icon - New mail count for a mail tag?
- Mem usage - PID - CPU usage Computing those are not trivial, so it is more a proof of concept than anything else, but it would be nice to...
Split some common sub menus to make them re-usable by other - Tag list - Client list - Signal list - Application
If some events happen in the background, it would be nice to know Example: "A new client have been added to "Tag 3"" "Transmission crashed" "Konversation has been to urgent"
Always communicate using signals. This is a little slower, but _much_ cleaner and easier to debug.
First of all, everybody else (but Awesome) do this. And then, all application get the mouse_release event without a mouse_press because Awesome ate it. This should be fixed in awful.menu...
- all item styles need to support it - all item layout need to add a dynamic property callback or a set_map handler on the "overlay property" - Implement a...
hover button1 button2 button3 ... button8 enter tab multiple can be selected at once Related to the "state" issue