On Mon, May 25, 2009 at 13:45, Julien Danjou <[email protected]> wrote: > At 1243244557 time_t, Julien Danjou wrote: > Pushed into 'next'; testing welcome, as usual.
Thanks a lot, the problem described is gone. By the way: I've previously experienced a noticeable slowdown when running root.keys() on tag change. Before the recent commits in next (when still using arrange hook) it was negligible and only really visible when holding down my awful.tag.viewnext() shortcut which effected in the tag switching (screen/taglist updates) looking a bit 'choppy'. I'm yet to make conclusive tests but I've been under impression that it's a great deal slower after the whole property/hook commits in next. When I hold down the viewnext() shortcut: 1. the screen switches to next tag 2. client in that tag receives and looses focus while the screen/taglist is not even refreshed for as long as I hold the key 3. when I let go of the key screen is switched to whichever tag is in reality selected This can be tested/reproduced by adding this to default rc's awful.hooks.tags function: if view == "select" root.keys(globalkeys) end This is not a major issue but makes me think that there could be some improvement to be made in the way properties/hooks/events are handled there. -- To unsubscribe, send mail to [email protected].
