FVWM3 is coming along nicely. My time has mostly been spent working on getting FVWM3 playing nicely with multi-monitor setups. This means:
- Detecting when a monitor is plugged in;
- Detecting when a monitor is unplugged;
- Giving the option to allow for desks/pages to be independent of each monitor;
All of this assumes that
libxrandr-dev is installed, and that the version of RandR is >=1.5 – this is because I make use of the
XRRGetMonitors() function which isn’t present in versions of RandR < 1.5, but 1.5 has been out for over three years, so I’m not too worried about compatability.
Presently, all of the above is largely still a work-in-progress, but I’ve made some strides in this such that I consider this to be functional enough that I need as much testing and feedback as I can get.
All of this work is currently on a branch called
ta/gh-22 – which originally was born out of Github issue #22 but I’ve now bundled way too much in there. Anyway, you can see that here.
This is the branch you should checkout and compile
The default behaviour for multiple monitors (if RandR is in use) is for them to all be treated as one global screen – the same behaviour as what Xinerama used to provide.
To change to having independent desktops per monitor, a command called
DesktopConfiguration has been created and accepts two values:
DesktopConfiguration global– all screens/desktops work as one`
DesktopConfiguration per-monitor– desktops are independent per screen
This can be added to FVWM’s configuration file, as well as being a toggleable command via
As per the commentary in GitHub issue #22, there’s on-going discussions, but I could do with more people testing that branch, and trying out the multi-monitor aspect.
Please spread the word, and to open issues or ask questions here – I don’t mind. But the more eyeballs I have on this, the easier it will be to fix bugs, and to get us closer to a release of version 1.0
At this point, FVWM3 will honour your existing
.fvwm2rc file, as there’s no breaking changes, save for the new commands in
FVWM3 which you’d need to add.
On the subject of releasing FVWM3, I’ve set up a project board which shows the things I need to do before that can happen. If anyone wishes to help with that – get in touch!