Re: [dev] dwm status click bug in multiscreen

btw.. enabling exec-on-mouse-over can create over 9000 processes. so it
should not exec until mouse-out or until the child process died.. this
is a bit more complex than the current approach, so i dont think its
necessary at all.

On 06/30/11 17:17, pancake wrote:
> I have just modified my config.h to run thingmenu.sh (which launches
> thingmenu with some common apps) just to test it a bit.. and the result
> is that the click event only works in my primary screen.
>
> If I click the StatusText of the second screen it just does nothing.
> (it works fine
> clicking the statustxt of the first screen)
>
> Is this a known bug? am I doing something wrong?
>
> static const char *menucmd[] = { "thingmenu.sh", NULL };
> static Button buttons[] = {
> { ClkStatusText, 0, Button1,
> spawn, {.v = menucmd } },
> }
>
> btw... is there any way to enable on-mouse-over event handling on this
> struct?
>
> it can be useful to just move the pointer to the status area to run a
> dzen or a thingmenu.
>
> --pancake
>
Received on Thu Jun 30 2011 - 17:31:39 CEST