Hi Thorsten,
> My problem is that nothing happens. Maybe signal property::x isn't the
> best way to start. A better way would be something like
I remember reading "properties are for internal use" in somewhere in
awful source.
You could use a timer, started within a function that calls
awful.mouse.client.move. Then connect it to your function which checks
for coordinates and move-resize client, but it should also check
whether mouse button is up and stop the timer. A little bit hacky.
So in my opinion better way is modifying a "copy" of
awful.mouse.client.move to compare coordinates.
> or 0 as soon as mouse_btn1 is up again (no more comparing all the time),
> but I could not find such a signal.
What about adding awful.button({ }, 1, nil, function(c) ... end) to
clientbuttons?
> awful.client.property.set(c, "x",
Also c:geometry({x=0, y=...}) would be better methinks.
I accept border actions would be nice, but why not assign 2 bindings
to clients to do just what you want.
--
Can Altıparmak
--
To unsubscribe, send mail to [email protected].
