On Mon, Dec 13, 2021 at 12:32:53AM +0000, Hegel3DReloaded wrote:
> On Monday, December 13th, 2021 at 1:18 AM, Dominik Vogt <dominik.v...@gmx.de> 
> wrote:
> > On Mon, Dec 13, 2021 at 12:12:30AM +0000, Hegel3DReloaded wrote:
> > > "Move +32768p +32768p",
> > Side note: The maximum valid position is +32767p +32767p. This
> > probably wraps around to -32768.
> That's it! If I redefine this to +32767p +32767p it starts to work as 
> expected.
> This will probably be ok to change no matter if used with FVWM 2 or FVWM 3.
> Something has changed in the new code apparently.

I've committed a patch to master that truncates out of range sizes
and positions to the max/min values instead of rejecting them.

Is there anything else in your config that's out of range?  The X
protocol is limited to 16 bit values for positions (signed) and
window sizes (unsigned).  I.e. -32768 to +32767 and 0 to 65535.

> but never mind, reducing it to 32767 fixes it.

-32768 is probably the better choice for "out of view" windows.
Fvwm doesn't use negative coordinates.


Dominik ^_^  ^_^


Dominik Vogt

Reply via email to