On Sat, Sep 13, 2014 at 11:46:21PM +0100, Thomas Adam wrote:
> On Sat, Sep 13, 2014 at 11:37:52PM +0100, Thomas Adam wrote:
> > I've no idea if this is a good way to go or not.  See comments in-line
> > as for the massive assumption I'm making, but Works For Me (tm).
> 
> This alone says to me "ditch it", to be honest.  As interesting an
> exercise as it is to try and maintain the status quo, this is one
> example where we might have to force a config file change to be more
> useful to us in terms of not making assumptions we can't maintain, such
> as the output from XRandR.

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

 * 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.

> I do appreciate that monitor names across machines change, but every
> other window manager I've seen just expects you to change those strings,
> irritating though that maybe.  But once they're there, there's no other
> maintanence needed from the user.

Yes, but other window managers probably don't allow the user to
specify geometry strings that address a specific monitor.  If you
cannot do anything with these monitors but move windows to the
other monitor manually, then of course there isn't much you can
change in the config file.

> Granted though someone could make judicious use of infostore to maintain
> some mapping and rely on expansion in the rest of the config.  That
> would then reduce some of the code I'd need to add to number monitors,
> etc.
> 
> Still, time will tell.  Maybe iterating over the outputs from XRandR in
> reverse order will be enough, although I don't know *what* that would
> mean for a non-linear arrangement, since XRandR allows for a grid MxN of
> potential outputs.  ;)

Ciao

Dominik ^_^  ^_^

-- 

Dominik Vogt

Reply via email to