| Re: [AD] Allegro 4.2 planning |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Allegro 4.2 planning
- From: Elias Pschernig <allefant@xxxxxxxxxx>
- Date: Tue, 19 Oct 2004 01:11:20 +0200
- Domainkey-signature: a=rsa-sha1; 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=hNAUme+SIH8PdaZ6FXCFK4c+QNbthVhyZGt/b7fKnoLhu8JdYk/3lXXNITg12BJIqmfcCu+e1IKsACkZxjTHW8yalSUjkkzhR9QBM/Ndgn0ROomyf6fRZ8p2C1o2WX7hqsxDgtd98r/svX6rzVAromDuq2DzX2XAAqDSGoCjvFE
>
> Is there any particular reason we couldn't do this for Allegro? It's what
> I'd expect KEY_A to mean anyway...
> Can't be helped though, changing it now would be breaking the API - but
> maybe for 4.3? Or is there some reason this is undesireable?
>
It wouldn't break the API.. the unix console as well as the Mac OSX
port already behave like that. (And I'm not sure how SDL behaves in
Windows, it might actually be like SDL there, since someone said
DirectX only reports scancodes. I somehow doubt it though.)
The reason for it is, if you make a game where you can e.g. move with
the keys "asdw" instead of the cursor keys. In this case, if you code
it in a lazy way and just check for KEY_A KEY_S and so on - it will
keep working with checking only the PC scancodes (just other letters
would be printed on those keys). IMHO, this only made sense when
Allegro was DOS only - since at that time, you could be sure who would
use it would also have a PC keyboard. With non PC keyboards, or for
more exotic keys, it can't work anyway. And allowing the user to
adjust the keys always is superior.