🚀 go-pugleaf

In article <101870@sun.Eng.Sun.COM> cmcmanis@sun.UUCP (Chuck McManis) writes:
->In article <783@pccuts.pcc.amdahl.com> (Tony Sumrall) writes:
->>  ...  There are times that it would be nice to have this info *before*
->> you open the window (like, so you could set the window's size prior to
->> the OpenWindow() call).
->
->When? I have been thinking about it and can't come up with a time when
->you need this information before you open the window. You could always 
->open the window, check the borders and then resize it down if you had
->to and exit if it wasn't big enough. Or open a small window, check 
->the borders, close it, set the sizes and reopen it.

But the point is that I don't *want* to flash a window at the user -- it
looks tacky. In VT100, since I have the user tell me how many LINES (s)he
wants to see (which is, I think, MUCH more friendly than forcing the user
to calculate pixels), I *assume* a top and bottom border size.  I'd
prefer to not have to guess.

->>inews fodder inews fodder inews fodder inews fodder inews fodder
->
->Change the include symbol to something like -> (rather than >) and you
->don't need this.

Yeah, I'm usually too lazy to do that.  You notice that I took your advice
this time, though :-)

->--Chuck McManis
->uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
->These opinions are my own and no one elses, but you knew that didn't you.
-- 
Tony Sumrall acs@pccuts.pcc.amdahl.com <=> amdahl!pccuts!acs

[ Opinions expressed herein are the author's and should not be construed
  to reflect the views of Amdahl Corp. ]