On Mon, Jul 29, 2019 at 10:36:57AM -0400 I heard the voice of
Stefan Monnier, and lo! it spake thus:
>
> FWIW, I haven't tried to use f.fullscreenzoom, instead I'm using F5
> in `evince` which AFAIK sets the FULLSCREEN hint.
>
> I assume ctwm handles both cases in the same way, but I just wanted
> to clarify.
Yeah, it does.
EwmhClientMessage()
-> EwmhClientMessage_NET_WM_STATE()
With fullscreen flag, sets it and then calls
-> EwmhClientMessage_NET_WM_STATEchange()
with EWMH_STATE_FULLSCREEN -> set window zoom to F_FULLSCREENZOOM
So it's identical to calling f.fullscreenzoom yourself from ctwm's
side.
Now, it also then winds up going out via EwmhSet_NET_WM_STATE() and
passing back an EWMH message to the window saying "hey, you're
fullscreen'd". So it's possible some apps might act a little
differently if you tell it directly to fullscreen so that _it_ sends
the 'state=FULLSCREEN' message itself, vs it just getting a
'state=FULLSCREEN' message from ctwm. But how it gets sized up and
positioned on the screen is probably going to be exactly the same[0].
[0] Unless the app then putzes with its own size/position or something
afterward. But who'd write an app that tries that hard to screw
with the WM and the user, anyway?
--
Matthew Fuller (MF4839) | [email protected]
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.
