From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: help-gnu-emacs@gnu.org, brakjoller@gmail.com
Subject: Re: w32-pass-lwindow-to-system (& ...rwindow)
Date: Sun, 24 Sep 2006 15:19:04 +0200 [thread overview]
Message-ID: <451685C8.50009@student.lu.se> (raw)
In-Reply-To: <u8xk9l9b7.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Sun, 24 Sep 2006 11:59:17 +0200
>> From: Lennart Borgman <lennart.borgman.073@student.lu.se>
>> CC: brakjoller@gmail.com, help-gnu-emacs@gnu.org
>>
>>
>>>> This behaviour is consistent with MS documentation. To avoid that
>>>> windows left and right keys open for example the run dialog with Win+r
>>>> you have to implement a low level keyboard hook.
>>>>
>>>>
>>> Can you give a pointer to the Microsoft documentation which says that,
>>> and/or documentation that explains how the LWIN-r combo works in terms
>>> of Win32 API calls, and why it bypasses the normal keyboard reading
>>> Emacs uses?
>>>
>>>
>> See the thread where we discussed this:
>> http://lists.gnu.org/archive/html/emacs-devel/2005-07/msg00448.html
>>
>
> I've re-read that discussion before asking the question. The only
> pointers I found there were to a CodeProject page, which just said
> that keyboard hooks were necessary, but didn't explain the issue any
> further. What I'm looking for is a more in-depth documentation,
> preferably official Microsoft one.
>
Unfortunately the documentation on LowLevelKeyboardProc or
WH_KEYBOARD_LL does not give a big picture. That was why I gave the link
above as a starting point.
http://windowssdk.msdn.microsoft.com/en-us/library/ms644985.aspx
I read a lot info about input processing on MS Windows, but
unfortunately I did not save links to those while switching pc. Anyway,
these links does not give the overall picture either but tells what to
do I believe:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/directx9_c/Disabling_Shortcut_Keys_in_Games.asp
http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/directx9_c_Dec_2004/directx/gamesforwindows/disablingshortcutkeys.asp
next prev parent reply other threads:[~2006-09-24 13:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 0:46 w32-pass-lwindow-to-system (& ...rwindow) B. T. Raven
2006-09-23 15:44 ` Eli Zaretskii
[not found] ` <mailman.7285.1159026303.9609.help-gnu-emacs@gnu.org>
2006-09-23 16:57 ` Mathias Dahl
2006-09-23 18:17 ` B. T. Raven
2006-09-24 12:59 ` Eli Zaretskii
2006-09-24 16:45 ` Eli Zaretskii
[not found] ` <mailman.7319.1159116339.9609.help-gnu-emacs@gnu.org>
2006-09-25 0:32 ` B. T. Raven
2006-09-25 3:21 ` Eli Zaretskii
[not found] ` <mailman.7336.1159154474.9609.help-gnu-emacs@gnu.org>
2006-09-25 11:55 ` B. T. Raven
2006-09-24 0:50 ` Lennart Borgman
2006-09-24 7:13 ` Eli Zaretskii
2006-09-24 9:59 ` Lennart Borgman
2006-09-24 12:48 ` Eli Zaretskii
2006-09-24 13:19 ` Lennart Borgman [this message]
[not found] ` <mailman.7293.1159059034.9609.help-gnu-emacs@gnu.org>
2006-09-24 3:34 ` B. T. Raven
2006-09-24 7:08 ` Eli Zaretskii
2006-09-24 10:19 ` Lennart Borgman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=451685C8.50009@student.lu.se \
--to=lennart.borgman.073@student.lu.se \
--cc=brakjoller@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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: link
Be 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).