Re: [dwm] We need a different Xinerama implementation

From: Anselm R. Garbe <>
Date: Fri, 15 Feb 2008 13:49:58 +0100

On Fri, Feb 15, 2008 at 01:24:05PM +0100, y i y u s wrote:
> 2008/2/15, Anselm R. Garbe <>:
> > On Thu, Feb 14, 2008 at 01:42:26PM -0600, Kurt H Maier wrote:
> > > What is the reason tags can't have flags? :)
> > >
> > > Think of it as tagging the tags themselves. Assigning the "screen 1"
> > > flag to a tag is just like assigning a "net" tag to a client. The
> > > difference would be that flags would be mutually exclusive; assigning
> > > a flag to a specific tag would first clear any other flags.
> >
> > Well I read through all responds and my favorit looks as the
> > following:
> >
> > I agree on Kurts approach. Having only 1 tagset (say 1,..,9) for
> > all screens, but have per-screen layouts and separate bars on
> > each screen (to avoid complexity). Now one can select certain
> > tags on any screen, but this selection will be mutiual exclusive
> > to other screens. Which might have the result that a certain
> > screen might not have any tags selected, hence only displaying
> > the wallpaper and its specific bar.
> >
> > This concept allows to keep navigation and tagging as simple as
> > it is atm.
> >
> Well, this is more or less the same thing I was proposing (clearier
> explained, my mails before mid day are a mess), but you still have the
> same problem: what if a client is tagged with tags in more than one
> monitor?

I think during all tag-related operations conflicting tags need
to be removed with the preference of the currently active

Which means during view() or toggleview() conflicting tags of clients are dropped with the preference of the screen acquiring the specific tag (e.g. say on screen 2 one views 2, while screen 1 has acquired tag "1" and there is a client being tagged 1+2 -- hence it will loose tag 1).

During tag() or toggletag() the same mechanism applies, but with
the preference of the screen of the new tag instead -- which
might move a window to a different screen and drop conflicting

> I reckon you will need a compromise here, but maybe there is a good
> solution I haven't thought about.
> I have also thought that you should take a different approach with
> floating clients. You should be able to move it wherever, don't matter
> in which monitor its tag it is. This could be confusing...

I consider implicit tagging of floating clients based on their
center point after a mouse-based move/resize operation. That's
the only sane solution I can come up with.

Kind regards,

 Anselm R. Garbe >< >< GPG key: 0D73F361
Received on Fri Feb 15 2008 - 13:49:58 UTC

This archive was generated by hypermail 2.2.0 : Sun Jul 13 2008 - 15:19:55 UTC