On Saturday, 4. January 2020 16:29, Thomas Adam <tho...@fvwm.org> 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 <RANDR name>' 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]: <<DEPRECATED>> 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