Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwvax!zazen!wuarchive!sdd.hp.com!spool.mu.edu!munnari.oz.au!ariel!ucsvc.ucs.unimelb.edu.au!wehi.dn.mu.oz!baxter_a
From: baxter_a@wehi.dn.mu.oz
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Window sticks under wb 2.0... (help me)
Message-ID: <1991May17.185042.24596@wehi.dn.mu.oz>
Date: 17 May 91 18:50:42 GMT
References: <1991May16.175636.1658@kberg.se>
Organization: Walter & Eliza Hall Institute
Lines: 19

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...
> 
> Any help appreciated.
> 
> 
> /svante

What I do, is test dimensions, and if greater than overscan, I open a standard
sized window/screen. 

Regards Alan