Path: utzoo!attcan!uunet!decwrl!bacchus.pa.dec.com!granite.pa.dec.com!mwm From: mwm@raven.pa.dec.com (Mike (My Watch Has Windows) Meyer) Newsgroups: comp.sys.amiga Subject: Re: 3000 vs Samsung Multisync... Message-ID: Date: 2 Oct 90 19:52:07 GMT References: <6132@amiga.UUCP> Sender: news@wrl.dec.com (News) Distribution: comp Organization: Missionaria Phonibalonica Lines: 26 In-Reply-To: jimm@amiga.UUCP's message of 28 Sep 90 20:45:05 GMT In article <6132@amiga.UUCP> jimm@amiga.UUCP (Jim Mackraz) writes: )By appropriate tweaking of the monitor settings and the overscan )modes, I can render on all of the screen. However, there is a line )above which the system won't move the mouse. If the sprite is positioned too high relative *to the hardware*, the initial words don't get fetched. So, there is a limit imposed in graphics.library (I presume the best possible limit). Retweak your screen some more: adjust the picture to move upwards, and return to the overscan preferences editor to move everything back downwards, to leave a few more "valid rows" out of sight off the top for the "clipped" portion of the sprite to use. I had already done that. The other thing I did (at John Lockhart's suggestion) to get more "valid rows" was change the pointer so the graphics were at the top of the sprite area used by intuition, instead of in the middle.