public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Oliver Schmidt <oschmidt-mailinglists@gmx.de> To: cygwin-xfree@cygwin.com Subject: Re: considering modifier keys after gaining focus Date: Tue, 10 Jan 2012 09:47:00 -0000 [thread overview] Message-ID: <4F0C0934.7010708@gmx.de> (raw) In-Reply-To: <4F0B2DC8.9030706@gmx.de> Hi, On 1/9/2012 7:11 PM, Oliver Schmidt wrote: > NEdit, press Ctrl+N for a new window, hold the Ctrl key and press S > (i.e. Ctrl+S) for saving. For the above NEdit example you have to disable the entry "Preferences / Default Settings / Tabbed Editing / Open File In New Tab" from NEdit's menu bar. Otherwise Ctrl+N will not open a new window. Of course every keyboard driven program that opens new windows with keyboard shortcuts will have problems with lost modifier key state. Moreover, if using my patch for "programmatically raising top level windows" ( http://cygwin.com/ml/cygwin-xfree/2011-08/msg00034.html ) the problem also occurs if a application raises windows by keyboard shortcuts. > I will try using GetKeyState tomorrow. I just wanted to be sure to get > the current key state when the window gets the focus. Ok, I tried using "GetKeyState" instead of "GetAsyncKeyState" and it also works. So it seems to be a good idea to switch to "GetKeyState". Best regards, Oliver -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2012-01-10 9:47 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-16 15:31 Oliver Schmidt 2011-08-21 8:44 ` Corinna Vinschen 2011-08-21 10:04 ` Oliver Schmidt 2012-01-08 15:23 ` Oliver Schmidt 2012-01-09 14:06 ` Jon TURNEY 2012-01-09 18:11 ` Oliver Schmidt 2012-01-10 9:47 ` Oliver Schmidt [this message] 2012-01-10 10:15 ` Oliver Schmidt 2012-01-11 17:16 ` Jon TURNEY 2012-01-12 12:19 ` Oliver Schmidt 2012-01-12 12:38 ` Oliver Schmidt
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4F0C0934.7010708@gmx.de \ --to=oschmidt-mailinglists@gmx.de \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).