| Re: [AD] Mouse cusor documentation |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Sunday 03 October 2004 15:57, Chris wrote:
> But the vtable function to set a custom hardware cursor should be able
> to indicate failure via a return value. Doesn't it already do this?
Of course. It's split into two parts: one that constructs the hardware
cursor from an Allegro bitmap, one that sets this. If the first fails,
then the second is not called. (This is controlled by the have_hd_cursor
in mouse.c)
> I think he means disable temporarilly, until it's shown on the screen
again.
If the mouse is not displayed on the screen, there is no hardware cursor
and Allegro uses the software cursor. I'm not sure, I think I said that
and I think that is what you meant too.
> So, IMO when enable_hardware_mouse is called, it should use the
> hardware/OS only when the target is "screen" (not the physical screen,
> since page flipping/scrolling can change what's in view and where, but
> the pointer to the screen bitmap), and the OS/hardware can accept the
> pointer bitmap.
It already does that.
Evert