Hi, Ok, it seems to work now... i did a system upgrade and some of the updated things were xorg stuff so i guess that was the root of the problem. thanks for all the good work you're doing on this project,
Yussi. On 07/07/12 12:41, Yussi wrote: > Hi Uli, > I did as you suggested, but it didn't work (I assume that print() > outputs to .xsession-errors) I than put in place the awesomerc.lua, and > buttons are still not responsive (I can't open the menu with a click or > switch tags that way). > Strangely, when i tried to put a connect_signal on a wibox, it did work > just fine. I assume that either the problem is in the build, or that > it's xcb or a related library that is the cause, but i wouldn't know > where to begin looking. > > thank you very much for the help, > > Yussi. > > On 07/07/12 11:32, Uli Schlachter wrote: >> On 07.07.2012 09:20, Yussi wrote: >>> Hi, >>> I recently updated my installation to the latest (unstable) build and >>> have experienced some problems ever since. In particular, widgets no >>> longer respect mouse::enter/mouse::leave( Wiboxes do) and buttons >>> stopped working altogether. >>> There's a snapshot of my configs at >>> https://github.com/yussidivnall/awesome-config >> >> Wow. What a mess. >> >> I assume you mean z.logs.panel, because the other places mentioning >> mouse::enter/leave are networkz and logz and those aren't executed by your >> config and are code for 3.4. >> >> I can't spot anything special here. Just a normal textbox. To test, I added >> the >> following to the default config: >> >> mytextclock:connect_signal("mouse::enter", function() print("enter") end) >> mytextclock:connect_signal("mouse::leave", function() print("leave") end) >> >> This works fine. When I point at the clock widget, the enter/leave messages >> are >> printed as expected. >> >>> Any ideas? >> >> Could you perhaps try to come up with a simpler test case for reproducing >> this? >> >> Uli > -- To unsubscribe, send mail to [email protected].
