Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cbmvax!ken
From: ken@cbmvax.commodore.com (Ken Farinsky - CATS)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Window sticks under wb 2.0... (help me)
Message-ID: <21680@cbmvax.commodore.com>
Date: 17 May 91 13:51:33 GMT
References: <1991May16.175636.1658@kberg.se>
Reply-To: ken@cbmvax.commodore.com (Ken Farinsky - CATS)
Organization: Commodore, West Chester, PA
Lines: 21

In article <1991May16.175636.1658@kberg.se> svante@kberg.se (Svante Gellerstam) writes:
>I am developing an application that runs on its own screen. To find out
>what size to use, I look at the WB screen and use that size. This
>works ok under 1.3 and 2.0 when the screen image is all visible.
>
>The problem shows up when the user has defined an oversized screen
>(beyond overscan) for the WB. My program opens the screen ok, but the
>screen won't budge. I just cannot move it like the WB screen. This is
>semi-critical as the quit button is at lower right...
>-- 
>Svante Gellerstam		svante@kberg.se, d87sg@efd.lth.se

Try specifying the tag {SA_Overscan, OSCAN_TEXT}.  This will allow your
screen to scroll with only the text overscan portion visible.  If you
also set {SA_AutoScroll, TRUE} then your screen will autoscroll when
it is the _active_ screen.
-- 
--
Ken Farinsky - CATS - (215) 431-9421 - Commodore Business Machines
uucp: ken@cbmvax.commodore.com   or  ...{uunet,rutgers}!cbmvax!ken
bix:  kfarinsky