Re: [AD] 4.1.17

[Elias Pschernig <elias@xxxxxxxxxx>]

On Thu, 2004-12-02 at 02:20 +0100, Evert Glebbeek wrote:


> AL_FUNC(void, select_mouse_cursor, (AL_CONST int cursor));

AL_CONST makes no sense there, an int is always const in C.

Compilation stops here (I think I should put back the patch to make
warnings default, in WIP versions.):
src/mouse.c:40: warning: missing initializer
src/mouse.c:40: warning: (near initialization for `mousedrv_none.select_system_cursor')

and then here:
src/linux/lmsems.c:247: warning: missing initializer
src/linux/lmsems.c:247: warning: (near initialization for `mousedrv_linux_ims.select_system_cursor')

and here:
src/linux/lmseps2.c:264: warning: missing initializer
src/linux/lmseps2.c:264: warning: (near initialization for `mousedrv_linux_ips2.select_system_cursor')

I tested it (in linux), and it seems to work. Should update exmouse to
demonstrate the different cursors. And, there should be another function
set_mouse_cursor(int cursor, BITMAP *bmp) (or different name), similiar
to set_mouse_sprite. Or maybe set_mouse_sprite should always modify the
current one? Could also think about making the global mouse_sprite
always point to the current sprite.

Anyway, for 4.1.17, this one is ok to apply. We still have time for
4.2.0 to finalize the cursors API.

-- 
Elias Pschernig