mwm@raven.pa.dec.com (Mike (My Watch Has Windows) Meyer) (09/27/90)
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 -- Come rain, come hail, come sleet, come snow Mike Meyer You don't like to drive to slow mwm@relay.pa.dec.com You're always in the passing lane decwrl!mwm It's enough to drive me out of my brain
jimm@amiga.UUCP (Jim Mackraz) (09/29/90)
(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 placemwm@raven.pa.dec.com (Mike (My Watch Has Windows) Meyer) (10/03/90)
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.
<mike
--
Cats will be cats and cats will be cool Mike Meyer
Cats can be callous and cats can be cruel mwm@relay.pa.dec.com
Cats will be cats, remember this words! decwrl!mwm
Cats will be cats and cats eat birds.