Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Fri, 22 Jun 2001 20:30:47 +0200 From: Marius Gedminas To: cygwin@cygwin.com Subject: Re: cygwin 1.3.2 bug on non-us keyboard layouts Message-ID: <20010622203047.B2500@gintaras> Mail-Followup-To: cygwin@cygwin.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.18i X-URL: http://ice.dammit.lt/~mgedmin/ On Thu, Jun 21, 2001 at 02:34:08PM -0700, Jason Tiller wrote: > Sounds like you're saying that when uChar.AsciiChar != 0 && > dwControlKeyState has both the control (LEFT or RIGHT) and alt (LEFT > or RIGHT) set, you can be assured the keystroke is generated via AltGr > and should not be treated as META. Am I reading that right? Yes -- on NT. > *Sounds* good! Yeah, I think you hinted about that above. You're > saying that none of the characters generated via AltGr have their > ASCII values in the range of 0->31 or 127 (control characters)? I hope so. (AFICT, eventually everything depens on the keyboard layout designer. That applies to your previous question, too.) > It might be possible to try to rely on the physical keyboard layout as > opposed to the primary language, as we do now. Good idea. Windows allows one to choose e.g. German layout for the US English language. Marius Gedminas -- If you are angry with someone, you should walk a mile in their shoes... then you'll be a mile away from them, and you'll have their shoes. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple