basilisk-devel

[B2-devel] Hardware cursor acceleration in B2

[Gwenole B. <gb...@di...>]

Hi,

Does someone know how we could handle hardware accelerated cursors in=20
Basilisk II? SheepShaver uses a feature from MacOS >=3D 7.5.3 with PCI=20=

video drivers interface, but I have not found anything similar for=20
MacOS 68k. At some point, I wondered about patching the _SetCursor=20
trap, but would could color cursors and direct TheCrsr low-mem globals=20=

changes be handled?

Thanks,
Gwenol=E9.=

Re: [B2-devel] Hardware cursor acceleration in B2

[Christian B. <Chr...@un...>]

Hi!

On Tue, Nov 16, 2004 at 12:51:54AM +0100, Gwenole Beauchesne wrote:
> Does someone know how we could handle hardware accelerated cursors in 
> Basilisk II?

I never bothered trying to figure this out. ShapeShifter uses the Amiga
mouse pointer in windowed mode, but its shape doesn't follow the Mac cursor.
It just replaces SetCursor with a "move.w #-16,$8d0" to make the Mac cursor
disappear.

Bye,
Christian

-- 
  / Physics is an algorithm
\/ http://www.uni-mainz.de/~bauec002/

Re: [B2-devel] Hardware cursor acceleration in B2

[Gwenole B. <gb...@di...>]

Hi,

> I never bothered trying to figure this out. ShapeShifter uses the =
Amiga
> mouse pointer in windowed mode, but its shape doesn't follow the Mac=20=

> cursor.
> It just replaces SetCursor with a "move.w #-16,$8d0" to make the Mac=20=

> cursor
> disappear.

OK, it's a complete trap replacement then, and not a usual chained=20
patch. Though we can get the cursor image from there, what about color=20=

cursors? I believe SheepShaver has the same restriction anyway. A=20
solution for Basilisk II would be to patch _SetCCursor to disable the=20
native cursor. I suppose CrsrState will be reset by _SetCCursor itself.

Bye,
Gwenol=E9.=