Re: FVWM: Controlling initial size of a "gThumb" window

Stephen,

On Friday, 2019-06-21 15:29:05 -0400, you wrote:

> ...
> Style gThumb NoPPosition, InitialMapCommand Resize 20 20

I modified this to

   Style gThumb InitialMapCommand ResizeMove 56 93 -0p 6p

and, as I've already let everybody know, it worked.

So I tried the same with "evince":

   Style Evince InitialMapCommand ResizeMove 56 93 0p 6p

and that worked, too.  But when I opened a PDF annotation from within an
"evince" window, the sub-window was positioned and sized the same as the
main window.  So I did

   Style Evince InitialMapCommand Current (!Transient) ResizeMove 56 93 0p 6p

which solved the latter problem  but at the same time  stubbornly posit-
ioned the main window at "20p 0p".  I ended up splitting the single "Re-
sizeMove" command into two:

   Style Evince InitialMapCommand Current (!Transient) Resize 56 93
   Style Evince PositionPlacement 0p 6p

This worked,  but what's going on here?   Why is "ResizeMove" not posit-
ioning correctly when a conditional is involved?

Finally, I also experimented with "scantailor".  I ended up with

   Style scantailor InitialMapCommand Current (!Transient, !URxvt) \
                                              Resize frame 100 93
   Style scantailor NoPPosition, PositionPlacement 0p 6p

because without the "Current (...)" clause  again sub-windows were sized
the same as the main window, and without the "!URxvt" the terminal wind-
ow from which  I started "scantailor"  was unconditionally resized,  too
(does anybody have  any explanation for THIS?).   But what's worse: even
with the "NoPPosition"  (and also with "FixedPPosition")  in effect each
call to "scantailor"  placed the window exactly 15p lower  than the pre-
ceding call.  And I have not yet found a remedy for this.

Yes, there is a file

    ~/.config/scantailor-advanced/scantailor-advanced.ini

and yes, it contains a line

   nonMaximizedGeometry="@ByteArray(...)"

But removing this line  causes a default size to be used for the window,
upon terminating "scantailor" a new "nonMaximizedGeometry=" will be add-
ed to the "*.ini" file, and each following call to "scantailor" will ag-
ain place the window 15p lower than the preceding call.

Any takers?

Sincerely,
  Rainer

PS: Before I forget:

$ fvwm -V
fvwm 2.6.5 compiled on Jan 26 2016 at 23:13:57
with support for: ReadLine, RPlay, Stroke, XPM, PNG, SVG, Shape, XShm, SM, Bidi text, Xinerama, XRender, XCursor, XFT, NLS
$