Hi I'm using a custom statusbar with dzen, in a xinerama environment ( defaultGaps = [(15,0,0,0)] in config file) This starts well, however when I open a new window (term) on the second screen, the statusbar is overlapped by the terminal window. Anyone experienced this ? Lobzang ___________________ http://lobzang.free.fr
On Fri, Sep 14, 2007 at 10:55:23AM +0200, lobzang@free.fr wrote:
Hi
I'm using a custom statusbar with dzen, in a xinerama environment ( defaultGaps = [(15,0,0,0)] in config file) This starts well, however when I open a new window (term) on the second screen, the statusbar is overlapped by the terminal window.
Anyone experienced this ?
Perhaps you need to explicitly define a defaultGap for the second screen, eg: defaultGaps = [(15,0,0,0),(15,0,0,0)] ? (I haven't tried this: my defaultGaps is [(0,15,0,0),(0,0,0,0)], ie I've explicitly set the gaps to be different on two screens.) -Andy -- Andy Gimblett Computer Science Department University of Wales Swansea http://www.cs.swan.ac.uk/~csandy/
lobzang:
Hi
I'm using a custom statusbar with dzen, in a xinerama environment ( defaultGaps = [(15,0,0,0)] in config file) This starts well, however when I open a new window (term) on the second screen, the statusbar is overlapped by the terminal window.
the status bar gap field is a list of geometries for each physical screen. to have a gap on the second screen, you'd use something like: = [(15,0,0,0), (15,0,0,0)] we might default to running the same gap on all screens -- perhaps that is what most people expect? -- Don
On Fri, Sep 14, 2007 at 10:24:29AM -0700, Don Stewart wrote:
lobzang:
Hi
I'm using a custom statusbar with dzen, in a xinerama environment ( defaultGaps = [(15,0,0,0)] in config file) This starts well, however when I open a new window (term) on the second screen, the statusbar is overlapped by the terminal window.
the status bar gap field is a list of geometries for each physical screen. to have a gap on the second screen, you'd use something like:
= [(15,0,0,0), (15,0,0,0)]
we might default to running the same gap on all screens -- perhaps that is what most people expect?
Is there any way we can detect when a program appears to be a status bar? Then we could simply adjust the gaps to compensate, which I suspect is what people would really expect... -- David Roundy Department of Physics Oregon State University
droundy:
On Fri, Sep 14, 2007 at 10:24:29AM -0700, Don Stewart wrote:
lobzang:
Hi
I'm using a custom statusbar with dzen, in a xinerama environment ( defaultGaps = [(15,0,0,0)] in config file) This starts well, however when I open a new window (term) on the second screen, the statusbar is overlapped by the terminal window.
the status bar gap field is a list of geometries for each physical screen. to have a gap on the second screen, you'd use something like:
= [(15,0,0,0), (15,0,0,0)]
we might default to running the same gap on all screens -- perhaps that is what most people expect?
Is there any way we can detect when a program appears to be a status bar? Then we could simply adjust the gaps to compensate, which I suspect is what people would really expect...
yes, its hard though. EHWM. jcreigh spent ages looking at this for all the dock apps. then trying to extract the geometries they want, and set the status bar automagically. Jason, care to elaborate on the difficulties? -- Don
On Friday 14 September 2007 12:29:59 David Roundy wrote:
On Fri, Sep 14, 2007 at 10:24:29AM -0700, Don Stewart wrote:
lobzang:
Hi
I'm using a custom statusbar with dzen, in a xinerama environment ( defaultGaps = [(15,0,0,0)] in config file) This starts well, however when I open a new window (term) on the second screen, the statusbar is overlapped by the terminal window.
the status bar gap field is a list of geometries for each physical screen. to have a gap on the second screen, you'd use something like:
= [(15,0,0,0), (15,0,0,0)]
we might default to running the same gap on all screens -- perhaps that is what most people expect?
Is there any way we can detect when a program appears to be a status bar? Then we could simply adjust the gaps to compensate, which I suspect is what people would really expect...
There are some ways, there are a few properties in EWMH, STRUT and DOCK IIRC. We'd need to patch dzen/xmobar to actually use these properties. Cheers, Spencer Janssen
On Fri, Sep 14, 2007 at 12:44:09PM -0500, Spencer Janssen wrote:
On Friday 14 September 2007 12:29:59 David Roundy wrote:
On Fri, Sep 14, 2007 at 10:24:29AM -0700, Don Stewart wrote:
lobzang:
Hi
I'm using a custom statusbar with dzen, in a xinerama environment ( defaultGaps = [(15,0,0,0)] in config file) This starts well, however when I open a new window (term) on the second screen, the statusbar is overlapped by the terminal window.
the status bar gap field is a list of geometries for each physical screen. to have a gap on the second screen, you'd use something like:
= [(15,0,0,0), (15,0,0,0)]
we might default to running the same gap on all screens -- perhaps that is what most people expect?
Is there any way we can detect when a program appears to be a status bar? Then we could simply adjust the gaps to compensate, which I suspect is what people would really expect...
There are some ways, there are a few properties in EWMH, STRUT and DOCK IIRC. We'd need to patch dzen/xmobar to actually use these properties.
That sounds like a good plan. And if we make this behavior configurable, perhaps users could set their config files to dynamically identify "struts" (which seems like a good name). i.e. start with code that only works with a few "supported" status bars that claim to be struts, and allow users to extend the strut identification code. -- David Roundy Department of Physics Oregon State University
* Spencer Janssen (sjanssen@cse.unl.edu) wrote:
There are some ways, there are a few properties in EWMH, STRUT and DOCK IIRC. We'd need to patch dzen/xmobar to actually use these properties.
Dzen does already set those properties, thanks to a patch Jason provided. To be precise, it sets the _NET_WM_STRUT_PARTIAL property, so if xmonad would also support that it would be perfectly usable out of the box :).
Cheers, Spencer Janssen
Bye, Rob.
participants (6)
-
Andy Gimblett -
David Roundy -
Don Stewart -
lobzang＠free.fr -
Robert Manea -
Spencer Janssen