[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] 4.1.17
- From: Angelo Mottola <a.mottola@xxxxxxxxxx>
- Date: Tue, 30 Nov 2004 11:36:01 +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:mime-version:content-type:content-transfer-encoding; b=J9VprQ0MYcRd7S6GIqzGLn4Vnp2kZ6d67CBvuJvkvaVy/TwqyrbVPqZG6FyvX/ipT0GnzJuW1N1fDWIopvoOfKJdAoGPWxa6CGZlh2eQoyN1fL8ipxx2lAlsrHgAIDEeaxoZ871D92s0LSs4HTyuQmo0Pr1kgZb6EJRodQyrCOg=
>>I hope to find the time but I can't guarantee... I have an exam in 10
>>days. For when do you plan to release 4.1.17?
>
> Well, the plan was tomorrow, but I guess that may shift yet again...
I have commited the OSX hardware mouse cursor patch yesterday, so we
can remove it from the TODO list :)
>>And what other features are missing from MacOS X apart from the hw
>>cursor? You make me worry... ;)
>
> Can't think of any :)
> Maybe I just assumed there were others because END_OF_MAIN() keeps poping
> up as something we can't solve on MacOS X...
> Oh yeah, does keyboard detection work well on MacOS X? Or do all Macs just
> have the same Mac keyboard? ;)
yes, END_OF_MAIN() cannot be removed from the OSX port, I'm sorry. Too
many Cocoa issues and threading issues...
About keyboard handling, the OSX port work this way: the system events
pump deals with all events, including keypress events. When a keypress
event is received, attached to it is also the ascii representation of
that key, already in the current system keyboard mapping. Allegro just
returns this in readkey()...
--
Angelo Mottola
a.mottola@xxxxxxxxxx
http://www.ecplusplus.com