1.1.0

[ThomasAdam]

For this release, there have been some changes which might break some configs.

The following notes will help with the upgrade to this version.

---

• build: fix Xft/Freetype/Fontconfig check by @ThomasAdam in build: fix Xft/Freetype/Fontconfig check #956

This change has made XFT a required dependency, rather than an optional one. If XFT is not found at ./configure time, an error is produced. It is therefore suggested all distro packagers are made aware of this.

---

• Goto{Desk,Page,DeskAndPage}: use 'screen' keyword by @ThomasAdam in Goto{Desk,Page,DeskAndPage}: use 'screen' keyword #967

Other commands in fvwm3 which can be used for specific screens (monitors) have always prefixed that with the literal screen keyword, for example: EwmhBaseStruts screen eDP-1 0 0 0 0. This change makes it so that the following commands also do the same thing:

• GotoDesk
• GotoPage
• GotoDeskAndPage

Before this version, such commands would have specified their screen parameter literally as in: GotoPage eDP1 0 0. This made parsing that difficult, so now this must be changed to:

GotoPage screen eDP1 0 0

---

• FvwmPager: present overview of all monitors if "Monitor:" is not used by @ThomasAdam in FvwmPager: present overview of all monitors if "Monitor:" is not used #978

This change is big -- and is listed here as a breaking change, only because of the number of different aspects it introduces. A separate video will be produced to highlight some of the more visual changes.

The key change here to FvwmPager is that if it is configured without a *FvwmPager: Monitor XXX directive, then the overview produced is a global view across all monitors. This was always the case, except now, the pager is aware of clicks into the pager being related to a specific monitor.

With DesktopConfiguration set to global, this works as it always did, as all connected monitors are going to change to the specific desk or page, regardless of what has been clicked in the pager.

With DesktopConfiguration set to per-monitor, the pager understands clicks relative to the monitor that area represents, and will therefore change to that specific desk or page.

Other changes include supporting the view of windows when DesktopConfiguration is set to shared.

A new option, MonitorLabels will print out the names of the connected monitors (from RandR) which makes visualising which monitor is focused on which desk helpful, as well as functional, as they can be clicked on to move to a specific desk.

XXX: link to YT video.

---

• Remove single screen support, -s. by @somiaj in Remove single screen support, -s. #977

Before RandR as a protocol existed, if you wanted to run fvwm on specific monitors, you would have needed to run fvwm on them as separate displays. The downside to this was that you wouldn't have been able to move windows between different running instances.

fvwm3's RandR support and DesktopConfiguration per-monitor setting makes this much easier to handle, without the restrictions mentioned. Therefore, the -s option to fvwm3 has been removed.

---

For the rest of the details, see:

Full Changelog: 1.0.9...1.1.0