On 15.01.2012 16:55, Anurag Priyam wrote: > On Sun, Jan 15, 2012 at 8:49 PM, Uli Schlachter <psyc...@znc.in> wrote: >> So I guess just a new patch which fixes this problem via the new >> screen.by_coords(x, y)? > > I tried the attached patch (based on `screen.by_coords()), but I am > getting the following stack trace: > > W: awesome: luaA_dofunction:108: error while running function > stack traceback: > [C]: ? > /usr/local/share/awesome/lib/awful/placement.lua:110: in function > 'no_offscreen' > /usr/local/share/awesome/lib/awful/tooltip.lua:72: in function 'place' > /usr/local/share/awesome/lib/awful/tooltip.lua:86: in function > 'set_geometry' > /usr/local/share/awesome/lib/awful/tooltip.lua:101: in function 'show' > /usr/local/share/awesome/lib/awful/tooltip.lua:186: in function 'func' > /usr/local/share/awesome/lib/gears/object.lua:71: in function > 'emit_signal' > /usr/local/share/awesome/lib/wibox/init.lua:177: in function > 'emit_difference' > /usr/local/share/awesome/lib/wibox/init.lua:202: in function 'func' > /usr/local/share/awesome/lib/gears/object.lua:71: in function > 'emit_signal' > /usr/local/share/awesome/lib/wibox/init.lua:214: in function > </usr/local/share/awesome/lib/wibox/init.lua:213> > error: /usr/local/share/awesome/lib/awful/placement.lua:110: bad > argument #2 to '?' (number expected, got userdata)
> + local screen = c.screen or capi.screen.by_coords(geometry.x, > geometry.y) > local border = c.border_width > - local screen_geometry = capi.screen[c.screen].workarea > + local screen_geometry = capi.screen[screen].workarea Oh. My function already returned the screen object and not just the screen index. Anyway, already reverted it away. :-) -- - Captain, I think I should tell you I've never actually landed a starship before. - That's all right, Lieutenant, neither have I. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
