darcs patch: the gaps list should be filled with the default value ...

hi,
this corrects what I believe was and is a bug in the original code: the gaps
list should be filled with the default values set in Config.hs. We are
simulating a xinerama setup, but we have just one set of gaps.
ciao
andrea
Thu Jul 5 00:41:10 CEST 2007 Andrea Rossato

Andrea Rossato
this corrects what I believe was and is a bug in the original code: the gaps list should be filled with the default values set in Config.hs. We are simulating a xinerama setup, but we have just one set of gaps.
ciao andrea
Thu Jul 5 00:41:10 CEST 2007 Andrea Rossato
* the gaps list should be filled with the default value from Config.hs
I have a Xinerama setup. Only the first monitor has a gap, and only it displays the two dzen2 instances. (I use something very close to the suggested setup in XMonadContrib/scripts/run-xmonad.sh.) I like it. Though I do have to admit that sometimes I think it could be nice if the dzens would follow the focus. Kai

On Thu, Jul 05, 2007 at 09:41:03AM +0200, Kai Grossjohann wrote:
I have a Xinerama setup. Only the first monitor has a gap, and only it displays the two dzen2 instances. (I use something very close to the suggested setup in XMonadContrib/scripts/run-xmonad.sh.)
This patch is not going to modify the behaviour of XMonad in a Xinerama setup, but the way layoutScreens sets up a fake xinerama setup. If a workspace shows up in the second (fake) screen (without gaps), when you will apply Operations.rescreen the windows in that workspace will now have a rectangle that is going to overlap with the gaps in their original (unmodified) workspace. This patch takes care of creating fake screens with the same gaps of the first (real) one. I do not have a xinerama setup and so I could get something wrong, but I think this should be the expected behaviour of layoutScreens. ciao andrea

On Thu, Jul 05, 2007 at 09:41:03AM +0200, Kai Grossjohann wrote:
I have a Xinerama setup. Only the first monitor has a gap, and only it displays the two dzen2 instances. (I use something very close to the suggested setup in XMonadContrib/scripts/run-xmonad.sh.)
I like it.
If you change your mind, and want gaps on multiple screens, just add more gap-tuples to the gap list in Config.hs; eg, the following puts a 15-pixel gap at the bottom of both screens: defaultGaps :: [(Int,Int,Int,Int)] defaultGaps = [(0,15,0,0),(0,15,0,0)] To a place dzen instance on the second screen, use the -x and -y command line flags judiciously. The x & y values you need will depend very much on your setup, the sizes and relative placements of the screens, etc. If you run multiple dzens, you probably also need to know about and use the -w flag, which restricts its width. By default a dzen will take up the entire screen (in fact, I _think_, go across multiple screens), potentially obscuring other dzen instances, so with more than one dzen running, this is essential (in my experience at least).
Though I do have to admit that sometimes I think it could be nice if the dzens would follow the focus.
Ah now that's a whole different ball game, I guess. :-) Hope this helps (someone), -Andy -- Andy Gimblett Computer Science Department University of Wales Swansea http://www.cs.swan.ac.uk/~csandy/

Andy Gimblett
To a place dzen instance on the second screen, use the -x and -y command line flags judiciously. The x & y values you need will depend very much on your setup, the sizes and relative placements of the screens, etc.
Isn't there a Xinerama patch for dzen somewhere? I vaguely remember this being the case, but it's been too long since I downloaded and installed it. I do "dzen2 -xs 1" (but still use -w and -x because I have two of them). Kai

* Kai Grossjohann (kai.grossjohann@verizonbusiness.com) wrote:
Isn't there a Xinerama patch for dzen somewhere? I vaguely remember this being the case, but it's been too long since I downloaded and installed it. I do "dzen2 -xs 1" (but still use -w and -x because I have two of them).
dzen comes with Xinerama support by default, it is a compile time option though. I.e. simply follow the comments in 'config.mk' to enable Xinerama. If 'config.mk' does _not_ include comments on Xinerama you should consider upgrading dzen as there were some bugfixes and improvements lately. Current version is 0.5.0 though the svn trunk has some code cleanups and fixes so that's the most stable version at the moment. See http://gotmor.googlepages.com/dzen for any further details.
Kai
Bye, Rob.

On Thu, 5 Jul 2007 00:45:45 +0200
Andrea Rossato
hi, this corrects what I believe was and is a bug in the original code: the gaps list should be filled with the default values set in Config.hs. We are simulating a xinerama setup, but we have just one set of gaps.
ciao andrea
Thu Jul 5 00:41:10 CEST 2007 Andrea Rossato
* the gaps list should be filled with the default value from Config.hs
Seems reasonable. Applied.
participants (5)
-
Andrea Rossato
-
Andy Gimblett
-
Kai Grossjohann
-
Robert Manea
-
Spencer Janssen