Hi all,

Please can I ask any willing volunteers reading this to take a look at the
master branch of FVWM3 and try it out [0]?

Your current configs will be valid (FVWM3 will look in the same locations as
fvwm2), minus the deprecation of the Xinerama* commands.  Previous module
support for Xinerama is not available at the moment; to be added in later on.

You can compile and install FVWM3 alongside FVWM2; the namespaces/versioning
is different, so it won't clobber FVWM2.  The FVWM3 binary is called 'fvwm3'.

What I'm hoping for right now is the bare-bones functionality of:

* Correct screen detection (that is, correct number of physical screens) --
  this is currently printed to STDERR when FVWM3 starts up, so check there;
* Commands such as MoveToScreen with a valid RandR monitor name works;
* The 'Screen <RANDR name>' conditional works for All/Any/Current, etc
* Monitors can be added/removed/changed, and FVWM3 shouldn't need a restart to
  pick up on any changes;
* FvwmIdent should report which monitor a specific window is on correctly

What isn't working:

* Rotation isn't support yet, and there's only a stub for RRChangeNotify events,
  although FVWM3 will call "All Placeagain" by default.  It might look weird,
  but I'll change that for a dedicated function(s) later on;
* Modules don't know which monitor they're on, so FvwmIconMan for example is
  going to struggle with a resolution set to 'Screen'.

I'm aiming for everything mostly behaving the same way it used to with
Xinerama, but this time with RandR.

Any feedback is going to be greatly received, believe me.  I've given this
only the lightest of testing, and it seems to be working OK for me, but I'm
hoping those of you brave enough will start flooding me with bug reports [1].

Thanks!

Thomas

[0]:  https://github.com/fvwmorg/fvwm3
[1]:  https://github.com/fvwmorg/fvwm3/issues

Reply via email to