Re: FVWM: FVWM3: RandR support ready for testing
On Saturday, 4. January 2020 16:29, Thomas Adam wrote: > 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; Works. > - Commands such as MoveToScreen with a valid RandR monitor name works; Works. > - The 'Screen ' conditional works for All/Any/Current, etc I don't know how to test it. I have tried in FvwmConsole "All (Screen DP1) Iconify", but stderr says: [fvwm][CreateConditionMask]: <> Use comma instead of whitespace to separate conditions > - Monitors can be added/removed/changed, and FVWM3 shouldn't need a restart > to > pick up on any changes; If new monitor is added either before X login or with "xrandr --output eDP1 --mode 1920x1080 --primary --output DP1 --mode 2560x1440 --right-of eDP1 --noprimary" Half of the X apps windows opened on the new DP1 screen (okular, mate-terminal, xpdf, FvwmScripts) does not have focus (I'm using SloppyFocus policy). Gvim for example has the focus. Fvwm's "Restart" command solves this. Sometimes (before Restart), if I move mouse pointer outside unfocused window and then back in but only to the titlebar, it gets focus, but loses it when I proceed with mouse pointer from titlebar into the windows. Typing with keyboard on new nonprimary display is not posible in most of the X apps prior to Restart. Is this something known or should I open issue on github? > - FvwmIdent should report which monitor a specific window is on correctly Works. ... one of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs. -- Robert Firth
Re: FVWM: FVWM3: RandR support ready for testing
Can a (64 bit) compiled version be put in bin for those of use that don't have a compiler? I don't think theres much if any that are OS dependent. I just pull fvwm from whichever pkgs has the latest version and it works. I'm actually running puppy xenial. Thanx
FVWM: FVWM3: RandR support ready for testing
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 ' 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
