| Re: [AD] XIM patch for Allegro 4.1.x |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] XIM patch for Allegro 4.1.x
- From: Elias Pschernig <allefant@xxxxxxxxxx>
- Date: Tue, 23 Nov 2004 19:28:55 +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=F5rc5sTmvOC4R8kZr3rkfcE21ta7BfsZsuTK1IO+DUkg3HFfBpFJP9HQ3a/Da8mhcBn9axFA9lWKOcyPFrbSebFy+Syn4LwCoOfCR37GJEudJtjp/T6GoD5G+WsLMDGJKFfDN1r12OSp5guQ6uPFZ2WtJWeRA9ewqMjBZD9+CFk=
>
> Great. That basically makes it Windows-only - which may make it worthwhile
> to consider if we can eliminate it completely (it could stay for DOS of
> course).
Yes, that's what I'm hoping. Allegro programs must be the only windows
programs who can't get the code a key produces, but need to lookup the
language settings and then translate with custom tables.
>
> > Yes, I was wondering about that as well.. probably makes sense to use
> > the Allegro names for all the modifier keys (not thinking about the poor
> > Sunos or Darwin users).
>
> As an alternative, may I be picky and suggest we do the name change only on
> Linux, or maybe on PCs only?
>
Actually, let's just not worry about this for now. If X11 reports
AltGr as ISO_level3_Shift_key - then we can assume that's the name of
that key - future X11 versions may have this fixed anyway.