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 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.
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. ;)
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
