Re: Plan E (was: [RFC] Titlebar code)

On Tue, 15 Sep 2009 00:06:19 +0200 (CEST) lukash lukk...@email.cz wrote: Lastly, if clients and widgets have common properties inherited from windows, how will these properties be handled on, for example, the icon widget in the example above, ie. in a widget inside a widget? Seems like a

[awesome bugs] #622 - Awesome keeps loading default theme

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#622 - Awesome keeps loading default theme User who did this - koniu (koniu) Reason for closing: Duplicate Additional comments about closing: Duplicate of FS#611

Re: Plan E (was: [RFC] Titlebar code)

Hi lukash, It'd be nice if your MUA can wrap lines at ~72 chars. :) At 1252965979 time_t, lukash wrote: 2. - that would need the .widgets table where you would set the layout, which you (jd) want to remove. IMHO, you should have this information anyway, either only as an array in C that

Re: Plan E (was: [RFC] Titlebar code)

On 15.9.2009 10:47:47 Julien Danjou jul...@danjou.info wrote: It'd be nice if your MUA can wrap lines at ~72 chars. :) Yes, I'll try :) I'm sorry Having layout written in C is just more limiting than having them in Lua and brings nothings but less extendability (is this a word?). Except for

Re: Plan E (was: [RFC] Titlebar code)

At 1253017547 time_t, lukk...@email.cz wrote: Except for less extendability (I think it is :) it brings speed. Speed? Why do you want to bring speed? Is it currently slow? Speed for speed brings nothing. I'm not sure if you have any experience with lua speed in awesome, I just found this:

Mouse motion detection

Hi there, I am trying to write a little odometer widget to have mouse coordinates displayed somewhere in the status bar for example (a very unuseful so indispensable stuff ;-)) There are many way to do this: - use a timer: each X seconds grab the mouse coordinates using the capi

Re: Mouse motion detection

On Tue, Sep 15, 2009 at 04:46:04PM +0200, jul...@danjou.info wrote: Thanks for the quick answer. And you can miss events anyway. If you update every 0.1 seconds, maybe the pointer is at the same place or very near but the user did a very fast movement. :) Anyway, using such a short timer

Re: Mouse motion detection

At 1253027134 time_t, Sébastien Gross wrote: Anyway, using such a short timer resolution wouldn't let awesome spend time on that particular timer function ? It'll wake awesome very often, which is bad for CPU sleeping and all power management stuff, but that's your problem. ;-) I don't think

Re: Plan E (was: [RFC] Titlebar code)

Hi again, I've started to dig further into this plan, and will add a number of ideas/concepts/how-it-will-be things. Feel free to discuss. - We cares about tags only on top level object in the hierarchy: +--+ | root win | +--+

[RFC Patch] Move c:raise() to the focus signal

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, what do you guys think about the attached patch? I haven't test this at all yet, but it seems as if it makes sense to me. Testing the default config is icky. :( Uli - -- Do you know that books smell like nutmeg or some spice from a foreign

Re: [RFC Patch] Move c:raise() to the focus signal

On Tue, 15 Sep 2009, Uli Schlachter wrote: Hi, Testing the default config is icky. :( I can confirm that it works, and nothing is broken. -- Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618 -- To unsubscribe, send mail

Re: [RFC Patch] Move c:raise() to the focus signal

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Adrian C. wrote: On Tue, 15 Sep 2009, Uli Schlachter wrote: Hi, Testing the default config is icky. :( I can confirm that it works, and nothing is broken. In that case feel free to steal it and sign it off for jd. Thanks for doing my

Re: [RFC Patch] Move c:raise() to the focus signal

On Tue, 15 Sep 2009, Uli Schlachter wrote: I can confirm that it works, and nothing is broken. In that case feel free to steal it and sign it off for jd. Thanks for doing my testing work. :D Ok, it is attached. -- Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 PGP FP: 02A5

Re: Plan E (was: [RFC] Titlebar code)

On Tue, 15 Sep 2009 14:34:13 +0200 (CEST) Julien Danjou jul...@danjou.info wrote: [...] Ok, I surrender :) I know I know nothing... Just keep it awesome! :) thanks lukash -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.

Multiple wibox on same 'position'

Hi, As some may know, two wiboxes cannot be created with same 'position' field in awesome 3.4, when in 3.3, the second declared wibox would appear just under the first. I worked on a small patch which modifies screen.c and awful/wibox.lua. Seems to be working for me so far (I work with one wibox

Re: [PATCH] rules: placement and geometry

For rules I created two table: data.set and data.postset. They contains setters and post setters. Postset is processed after set. I hope it solve problem with focus and dimenssion not applied in the good order. I renamed switchtotag in the same patch as it's a pretty new stuff and the old