[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] 4.1.17
- From: Elias Pschernig <allefant@xxxxxxxxxx>
- Date: Fri, 3 Dec 2004 15:55:37 +0100
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=go7eraTWityyijV3hqnMugr9pT+Iyzt0I7b8+YHEDYYzSbQMwIZ45tRKe6k0J7+9DCoUlahBAotfUW4Y5dNifw7F+Wcmuhr/gA8Bfl1XKLNtw8CWOMj5jxQ7eI80I0moYDfAX5EVSh4lw6HEPVfec30PDBAtTGoDyPvDIs25vgk=
> Basically, it's a debug aid. It prevents you from accidentally changing an
> input variable and screwing up because of that.
> Don't know, guess I'm used to doing this... may or may not be that useful.
> What's the convention with other Allegro functions? I thought it was like
> this, but I may be mistaken.
No other functions use this.
> But this isn't what the function does. It's specific purpose is to request
> the default system pointer, something that couldn't be done before.
> It *could* be changed to only do this if no custom bitmap has been set, but
> I'm a bit uncertain on how nicely this will fit with the current scheme.
Ok. But why did you add the default cursor shapes then? If all we want
is a function to display a system mouse cursor, they are not needed.
But if we have them, they should be modifieable by the user.