On Sun, Sep 14, 2014 at 12:25:12AM +0100, Dominik Vogt wrote:
> I wasn't talking about a config file change fvwm2 -> fvwm3.
> Consider this layout:
>
> +----------+ +------+ +-------------+
> | | | | | |
> | "1" | | 0 | | |
> | | | | | "2" |
> | | +------+ | |
> +----------+ | |
> +-------------+
>
> The user has a built in screen (0) and an external screen at home
> to the left of the builtin screen ("1") and another external screen
> at work that is to the right of the builtin screen.
>
> The user must (I say "must" because we're not talking about a
> random low quality wm but about "fvwm3") *must* be able to write
> one config file that works
Oh, I *see*. Right, I'm with you now. Sorry, I'm still very muchin the
mindset of fvwm2 -> fvwm3 migration.
> * If only screen 0 is present (0 is the primary screen).
> * If screen 0 and "1" are present (primary = "1")
> * If screen 0 and "2" are present (primary = "2")
>
> without changing the configuration file in between. More things
> that shouldn't require changing the config file:
>
> * Rearranging the monitors (i.e. "1" is to the right next time)
> * Replacing an external monitor with another one (e.g. bought a
> bigger monitor)
> * Adding a second external monitor, e.g. using "1" and "2" at
> the same time. (Of course this may require selecting a new
> primary monitor, but that would be only one config line).
>
> Well, maybe the user has to do the mapping manually, but hopefully
> just once.
That's certainly a different challenge. I'll add the above to the TODO
file.
-- Thomas Adam
