commit 33fae2594882ea5c511f38ebdba6a83ad6070cbf Author: Julien Danjou Date: Tue Mar 2 17:54:05 2010 +0100 change codename Signed-off-by: Julien Danjou commit 21d3d2aae56129f1450966babb3b8e5ccd2fa1c4 Author: Adrian C. (anrxc) Date: Fri Feb 26 21:25:35 2010 +0100 awful.widget: add progressbar set_max_value property The awful.widget.graph allows to change the maximum value a graph can handle, thus allows users to use widgets and scripts that don't scale the values down to 0 - 1 range. The progressbars did not allow this and worked with a hard-coded value of 1. Signed-off-by: Adrian C. (anrxc) Signed-off-by: Julien Danjou commit f41d7e270fb776990362acf8c265d6dd017b4f84 Author: Adrian C. (anrxc) Date: Tue Feb 23 03:23:14 2010 +0100 awsetbg: add fvwm-root support fvwm-root is a part of the FVWM window manager, and is one of those utilities that properly support transparency because it can retain and publish the Pixmap with which the background has been set. It supports XBM, XPM, PNG and SVG image formats, but is not very rich in options as opposed to habak or feh. Signed-off-by: Adrian C. (anrxc) Signed-off-by: Julien Danjou commit 9f537bcb37f1f2a352a90e44fe9c91710da009fb Author: Adrian C. (anrxc) Date: Sun Feb 21 00:58:07 2010 +0100 awful.menu: sanitize support for access keys Commit 87070ca introduced support for access keys in menus. Chosen character was "&", an XML entity that has potential to cause problems; if a user tries to add multiple access keys or just put an ampersand in the name of the item the menu will break. Breaking happened because ampersands were not escaped - first one was substituted and the rest were ignored, but not escaped which triggered a pango markup error. Signed-off-by: Adrian C. (anrxc) Signed-off-by: Julien Danjou commit b38569913c51ebd75e6ef0810063cf700edb921b Author: Matthias Schröder Date: Thu Nov 26 12:47:39 2009 +0100 awful.menu: support for access keys You can define a menuitem like before: awful.menu({ items = { { "&awesome", myawesomemenu, beautiful.awesome_icon }, { "open &terminal", terminal }, }) and the letters following the ampersand in itemname can be used as access key. (at least former fvwm users might find this familiar) When there are submenus open awesome ascends during the search from the current menu to the top level menu. The access key is shown underlined. There is no warning for multiple used keys, only the first one found gets the price. Signed-off-by: Julien Danjou commit 4299c5b184e15f6f102b1d8071c771a865fae326 Author: Julien Danjou Date: Thu Feb 18 10:04:01 2010 +0100 ewmh: remove _NET_WORKAREA support (FS#732) This fixes problem with Qt 4.6. Our implementation cannot be standard, and was not standard, so just stop using this EWMH crap. Signed-off-by: Julien Danjou commit 574c630a1b57ad350b82fed7a1208a8a4acc652e Author: Gregor Best Date: Tue Feb 16 17:54:45 2010 +0100 naughty: add suspend() and resume() This commit adds naughty.suspend() and naughy.resume() which allow suspension of notifications, which is useful e.g. when watching a movie, where notifications popping up all the time would be disturbing. While suspended, notifications are collected and displayed after naughty.resume() is called. Signed-off-by: Gregor Best Signed-off-by: Julien Danjou commit 0a87e031fe04d6ca49ff6fcf24a5f1989d087d92 Author: Andrei 'Garoth' Thorp Date: Tue Feb 16 14:16:17 2010 -0500 Fix naughty.destroy parameter documentation Signed-off-by: Julien Danjou commit adff92ca533f93bffa1de9974098f75de84bc8d4 Author: Uli Schlachter Date: Tue Feb 9 14:02:38 2010 +0100 property.c: Don't leave stuff on the lua stack property_update_wm_hints() pushes the client but never pops it. This is a really bad thing (tm). Signed-off-by: Uli Schlachter Signed-off-by: Julien Danjou commit bec9e24e7ff6bc98f8b3439a8426485ef8d19eb8 Author: Uli Schlachter Date: Tue Feb 9 13:58:06 2010 +0100 client_focus_update(): Balance the lua stack There is a push 15 lines before the push that is removed here, but the client that is pushed there was never popped. Bad. Fix this by letting luaA_class_emit_signal() do the needed pop for us. Signed-off-by: Uli Schlachter Signed-off-by: Julien Danjou commit 5f9bd088f29e9a7a42a08336e69ed6de08af6ba3 Author: Thomas Arendsen Hein Date: Sat Jan 23 17:43:53 2010 +0100 New images for maximized layout. Based on an idea by Steve Pomeroy (xxv) Signed-off-by: Julien Danjou commit 56c1fdf226835c9626d1227034e6422c0e0033c1 Author: Adrian C. (anrxc) Date: Sun Jan 10 21:30:35 2010 +0100 awful.rules: fix client tagging with multiple screens Commit a757dda replaced the awful.client.movetotag call with c:tags() in the tag property handler. Which introduced a regression when more than one screen is used. The awful.tag.withcurrent function was being called even when there was a valid tag property. Now the clients screen is set to the tag screen to ensure the client is moved to the correct tag and screen. Signed-off-by: Adrian C. (anrxc) Signed-off-by: Julien Danjou commit dfd6060a53cdf7d3a372117da40a8c8eefc991f9 Author: Adrian C. (anrxc) Date: Sat Jan 9 17:23:05 2010 +0100 awful.autofocus: improve client focus with multiple screens Changing screen focus to an empty tag leaves focus on a client on the previous screen, if a tag with clients is focused next the focus remains on the previous screen. Now awful.autofocus compares the tag screen and clients screen to learn if the focus should be given to a client on the focused screen. Client that gets the focus is selected from history, as usual. Signed-off-by: Adrian C. (anrxc) Signed-off-by: Julien Danjou commit a757ddabc4484a9369c30fb28327145df4f37673 Author: koniu Date: Fri Jan 8 15:26:21 2010 +0000 awful.rules: tag clients without flicker (FS#664) We unregister the default awful.tag.withcurrent 'manage' signal handler and have awful.rules.apply handle initial client tagging. Signed-off-by: koniu Signed-off-by: Julien Danjou commit a1f0669b642da258fb206b464a4fd59b8a730eb1 Author: koniu Date: Fri Jan 8 15:16:37 2010 +0000 awful.tag: register 'withcurrent' explicitly This explicitly registers withcurrent(c) as a manage signal handler so that it can be removed if necessary. Signed-off-by: koniu Signed-off-by: Julien Danjou commit d09c3c02e8f9caeb4b11d62b642d7f369d5d7a8a Author: Julien Danjou Date: Wed Jan 6 09:42:05 2010 +0100 Handle synthetic UnmapNotify events *correctly* Second try: Turns out I messed up with XCB_EVENT_SENT() and had a "!" too much. The old code already tried to cope with this, but forgot to actually unmap the window which it just set to withdrawn state. This time I tested the patch *again* and now I found even less bugs than on my last try. P.S.: I suck. Signed-off-by: Uli Schlachter Signed-off-by: Julien Danjou commit 9038c5165d22fe69fbbf6392361b0155fd0c6484 Author: Adrian C. (anrxc) Date: Mon Jan 4 23:37:16 2010 +0100 awful.wibox: sanitize height/width args to function new() When both height and width arguments are provided to the function new() there is a check to see if one of them was a screen percentage, and is expected to be a string. If the user provided absolute pixels, and argument is of type number awesome will crash. Now tostring is used to sanitize the arguments during this check. Signed-off-by: Adrian C. (anrxc) Signed-off-by: Julien Danjou commit b24348219e9a63db12e3074b3b2cc13019e47e0b Author: Alex Alexander Date: Tue Jan 5 09:52:43 2010 +0100 wibox: fix align awful.wibox.align() in 3.4.x gets the available screen area from capi.screen[screen].geometry. this can easily result in overlapping wiboxes since the work area provided does not account for existing wiboxes. In my configuration I use a vertical wibox positioned at the right and it half-overlaps my top wibox because it is streched and hard-coded to align at the middle. Signed-off-by: Julien Danjou