On Dec 10, 2007 4:11 AM, Chris 'Ducky' Chapin <[EMAIL PROTECTED]> wrote:
> > This is sort of what I've done. I run dwm at work with a 2 head xinerama > setup, so added a side attribute to the client struct and added a > function to toggle it. Then I just copied and adjusted the tile function > to display 2 mains and 2 stacks mirrored. This what a coworker has > dubbed the dumbbell layout: "[]==[]". =) > > -Ducky > I don't have a multi-head setup but I have used some at work. I think most of the time I had a notion of a primary screen and a secondary screen. Given that, I think it will be useful to designate one screen as the master screen displaying only master windows (with adjustable number of columns, I think a default of two is good) and the other screen as a stack screen with a multiple columns (I think three will be a good default). The rest remains the same except probably, restricting windows not to extend to the other screen automatically. Ritesh > Maarten Maathuis wrote: > > A shared tagging setup, but a flag to indicate primary or secondary > head. > > Sort of like adding an extra dimension to dwm. > > > > Maarten. > > > > On 12/9/07, Anselm R. Garbe <[EMAIL PROTECTED]> wrote: > > > >> Hi there, > >> > >> could you imagine that there is a way that dwm could be used in > >> a Xinerama environment and how that might look like? > >> Regardless if that is necessary or not for mainstream dwm, > >> I see the following possibilities: > >> > >> - aim multihead setup (distinct bars, tag sets and layouts for > >> each screen) > >> > >> - extend tile() into tile2() and tile3(), where tile2 assumes > >> one screen as master area (with the bar), and one screen as > >> stacking area (note, setmwfact won't have any effect here), and > >> tile3() would do similiar, but the third screen would be > >> stacking area as well. > >> > >> Are there other ideas? > >> > >> Regards, > >> -- > >> Anselm R. Garbe >< http://www.suckless.org/ >< GPG key: 0D73F361 > >> > >> > >> > >
