Anyone know of a way to display a window's geometry (e.g. 80x24 characters
or 400x300 pixels) while the user is resizing/moving the window?
Here's FVWM doing it:
http://imgur.com/hu6rFrC
twm and Openbox also do it.
Thanks,
Robert
screen[mouse.screen].geometry=> returned a table with key "x" "y"
"width" "height"
if c is a client object, then
c:geometry() => returned a table which structure is described above
On 09/29/2015 03:53 PM, Robert Fleming wrote:
Anyone know of a way to display a window's geometry (e.g. 80x24
Ah OK thanks for the quick reply!
Could register a function to a signal (awesome 3.4) to get this info
rendered into the screen as the mouse is moving around?
screen[mouse.screen].geometry=> returned a table with key "x" "y"
"width" "height"
if c is a client object, then
c:geometry() => retur
mouse.screen is auto updated when you move your mouse around the screen.
then use
screen[mouse.screen], which screen is a global table in awesome rc.lua,
to get the screen object.
On 09/29/2015 04:18 PM, Robert Fleming wrote:
Ah OK thanks for the quick reply!
Could register a function to a s
Hello,
are there some people here using inkscape (vector-based drawing
program)? There is actually a (small but annoying) problem when used
with awesome. Guide lines can be added (typically for attaching objects
on it) by dragging them from the rulers. The problem is that this is
understood b
Hi,
I have the same issue, so it's unlikely to be an error in your config.
Left-Clicking and dragging on any pixel that does not belong to the
document or to a button is interpreted as mod4+button1.
Best,
Szymon
On 2015-09-29 11:09, Raphael Plasson wrote:
Hello,
are there some people here
On Tue, Sep 29, 2015 at 11:54:03AM +0200, Szymon Hennel wrote:
> Hi,
>
> I have the same issue, so it's unlikely to be an error in your config.
> Left-Clicking and dragging on any pixel that does not belong to the document
> or to a button is interpreted as mod4+button1.
I don't have the issue. I
No problem here either, with the same versions as lilydjwg.
My config
https://github.com/silverhammermba/.files/blob/bet/awesome/.config/awesome/rc.lua
On Tue, Sep 29, 2015 at 9:31 AM, lilydjwg wrote:
> On Tue, Sep 29, 2015 at 11:54:03AM +0200, Szymon Hennel wrote:
> > Hi,
> >
> > I have the sa
I have just discovered that the behavior is more complex than just
treating any click as mod4+button1 : Inkscape jumps between screens, but
not within a single screen. If I reduce my setup to only one screen,
there is no problem. Let me explain this better :
I have 2 screens, both showing thei
Yes, I have two screens. I also get the weird maximized behavior from
Inkscape but I think that is unrelated as everything else works fine.
On Sep 29, 2015 10:24 AM, "Szymon Hennel" wrote:
> I have just discovered that the behavior is more complex than just
> treating any click as mod4+button1 :
Interesting. Here's my config in case anyone is interested :
http://pastebin.com/s4wQSUvL
I will try to solve the problem and report back if I find anything.
On 2015-09-29 16:29, Maxwell Anselm wrote:
Yes, I have two screens. I also get the weird maximized behavior from
Inkscape but I thin
Weird indeed. I have the problem with the last debian sid version
(awesome 3.5.6-1 and inkscape 0.91-5+b2).
However, I tried with a new, empty user... no problem.
I copied the full .config/awesome from my main user to this test user...
no problem
I then copied the full .config/inkscape from mai
12 matches
Mail list logo
