From mint-bounce@lists.fishpool.fi Fri Apr 1 00:39:05 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de From: Henk Robbers To: mint@fishpool.com Subject: Re: [MiNT] New AES keyboard messages Date: Thu, 31 Mar 2005 23:40:27 +0200 User-Agent: KMail/1.5.4 References: <1111344400.12169.50.camel@taro.coolrunningconcepts.com> <424B0943.3000706@gabo.pl> In-Reply-To: <424B0943.3000706@gabo.pl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Disposition: inline Message-Id: <200503312340.27237.h.robbers@chello.nl> X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: h.robbers@chello.nl Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=0.6 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00, RCVD_IN_SORBS X-Spam-Level: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id j2VMd5XJ010015 On Wednesday 30 March 2005 22:17, Adam Kłobukowski wrote: > Hello > > I have idea of new type of messages AES could deliver to applications. > > The messages are Key pressed, Key released. > > Key pressed is sent only once when key is pressed, no mater what > keyrepeat would produce. > Key released is also sent only once, when key is released. > > That messages can be sent interleaved, ie when user presses multiple key > at the same time. > > That messages should be new class of the messages, not included in any > other class (esp. keyboard messages), for a call like event_multi. This > is so application/AES would not need to waste time for handling unwanted > keyrepeat messages. > > The main reason for adding this messages is SDL and gaming in overall > under AES. > > (btw. SHIF, ALT, CONTROL should be also sent as such messages) > > Technical details lik API/ABI are left for discussion. > > Thanks for Ozk for being interested. I remember similar question couple of years ago when I was still XaAES maintainer I reserved event MU_DYNAMIC_KEYBD for it, nothing more. Didnt spent further thoughts about it at the time. Presumely it was my intention to send the event when either a key was pressed or released. A bit in kstate could be spent. As for detection of single press of CTRL, ALT, SHIFT: This requires facilitating in low level keyboard driver (IKBD). Normally these states are only supplied in combination with scancode generating keys. I did implement the use of NKCC by XaAES via event MU_NORMKEYBD. In stead of scancodes you get normalized ASCII character values. This might be a good place to look into. (NKCC by Harald Siegmund uses scancode and TOS translation tables together with modifier keys for producing ASCII character codes independent of keyboard language.)