On Wed, Mar 6, 2024 at 10:51 AM Jaimos Skriletz <jaimosskril...@gmail.com> wrote: > > On Wed, Mar 6, 2024 at 10:45 AM Chris Siebenmann > <cks-f...@cs.toronto.edu> wrote: > > > > > > Is this intended behavior? I can't spot a strong statement either way in > > the current documentation for Move, although some of the wording sounds > > a bit odd if explicit Move positions are supposed to be screen relative. > > Move honors EWMHBaseStruts, which even if they are zero, are now set > per monitor. Due to this some computations don't work as you would > expect, since fvwm will adjust the window location to be inside the > working area of the current monitor. Does telling Move to ignore the > base strust fix your issue. I.e. add ewmhiwa to the end of each of > your Move commands. > > Move 3370p -0p ewmhiwa > > The other option is as you stated, make your move commands relative to > a specific monitor (instead of the current one) for when base strut > calculations are used. > > jaimos
I forgot to send my response to the list.
