Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!olivea!oliveb!amiga!jimm
From: jimm@amiga.UUCP (Jim Mackraz)
Newsgroups: comp.sys.amiga
Subject: Re: 3000 vs Samsung Multisync...
Message-ID: <6132@amiga.UUCP>
Date: 28 Sep 90 20:45:05 GMT
References: <MWM.90Sep26165134@raven.pa.dec.com>
Reply-To: jimm@amiga.UUCP (Jim Mackraz)
Distribution: comp
Organization: Kodiak Software, Mountain View CA 94041
Lines: 33

(Mike (My Watch Has Windows) Meyer) writes:
)I've just added a (used) Samsung multisync (which is supposedly a
)clone of the Nec Multisync II) to my 3000. While I'm glad to have it,
)there's one oddity that someone may be able to shed some light on.
)
)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. It acts like the mouse is
)above that point - letting me grab and move windows and screens - but
)the mouse stops moving up about 30 pixels below the top of the screen
)(both physical and Workbench).
)
)Anyone care to try and shed some light on this?
)
)	<mike

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).

I do not know if this is hardware row 0, 12, 20, or what.

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.

	jimm

-- 
--- Graciously hosted by but not associated with Kodiak Software. ---
"I've got great news.  That gum you like is going to come back in style."
						-the man from another place