On 20 January 2016 at 16:46, Dan Espen wrote:
> Tom, by "larger piece of work", I take it you mean you have to deal with
> rotations?
Yes---I wasn't too clear before, sorry. I'd like to see this change
implemented in terms of either Xinerama or RandR---that is, to use
their mechanisms for hookin
"Raimund Steger" writes:
> On Wed, January 20, 2016 14:56, Thomas Adam wrote:
>> [...]
>> But that's a much larger piece of work, believe me. But your patch
>
> No argument here, but from [1], section 8:
>
> "
> Clients MAY select for ConfigureNotify on the root window to be
> informed of screen
Hi,
This isn't the correct approach at all. You should start to consider
RandR here (getting rid of Xinerama in the process). In that way,
listening for RRScreenChangeNotify would do just as well. Relying on
ConfigureNotify on the root window without checking with RandR is the
failing here.
Bu
On Wed, January 20, 2016 00:00, Raimund Steger wrote:
> [...]
> Now after a couple of weeks filled with countless FVWM restarts, I've
> finally looked into building a patch (attached) that will at least update
> $[vp.width] and make FVWM popup menus be clipped correctly to the changed
> screen area
