On Tue, Jan 22, 2002 at 04:39:12PM +0100, Bo Thorsen wrote:
> Exactly! And this is what IMHO is the right way to do it. The reason I listed 
> the Sawfish implementation notes is that these shows real annoyances for 
> users and one way to implement it is by a boundary down between the two 
> monitors. Do you not think that these issues are annoying:
 
Ok, first off, sawfish has no capacity natively to do anything OTHER than
Xinerama, if you want it to support multiple monitors, so it's hardly a
good tool to use for comparisons.  I discount the --multi-head hack as real
support, because the author discounts it too.

> " * Preventing Windows from being mapped across heads

Don't use Xinerama and you're not mapping across heads.  Although why are
you using Xinerama in the first place if you don't want to be ABLE to "map
across heads"?

>   * Preventing Windows from being mapped in dead spots

Don't use Xinerama and you can't map a window into a "dead spot" because there
*aren't* any "dead spots".

>   * Edge resistance moving between heads

There's that moving windows between monitors again.  Why would this be
necessary, or desirable?  Start the app on the monitor you want it on in
the first place.

Is that *really* the only thing you find important about multi-head?

>   * Centered and Random placement modes place windows on the current Head"

Don't use Xinerama and windows *always* get placed on the head you want
them on because that's where you launched them.  You can even control which
head from a shell script or whatever you like (-display option exists for a
reason).  Try that with Xinerama.

Xinerama is meant for one, and only one thing.  Gluing multiple screens
togetheri with no seams.  That's ALL.  And it does that very well.  Not for
artificially imposing boundaries of where a window can go.  The whole idea
of it is that a window CAN span monitors... that you would WANT it to span
monitors...  otherwise, why use the feature in the first place?

If you want all these other things, then why are you using Xinerama and
trying to wedge the window manager's behavior into it, rather than NOT
using Xinerama and just enjoying the fact that you have them by default?

-- 
Marc Wilson
[EMAIL PROTECTED]
[EMAIL PROTECTED]

Reply via email to