WM_KEYDOWN,从lparam获取值?

时间:2010-11-08 19:02:30

标签: c++ c winapi

在MSDN上,对于WM_KEYDOWN定义,它说lparam的位包含:

Bits    Meaning
0-15    The repeat count for the current message. The value is the number of times the keystroke is autorepeated as a result of the user holding down the key. If the keystroke is held long enough, multiple messages are sent. However, the repeat count is not cumulative.
16-23   The scan code. The value depends on the OEM.
24  Indicates whether the key is an extended key, such as the right-hand ALT and CTRL keys that appear on an enhanced 101- or 102-key keyboard. The value is 1 if it is an extended key; otherwise, it is 0.
25-28   Reserved; do not use.
29  The context code. The value is always 0 for a WM_KEYDOWN message.
30  The previous key state. The value is 1 if the key is down before the message is sent, or it is zero if the key is up.
31  The transition state. The value is always 0 for a WM_KEYDOWN message.

http://msdn.microsoft.com/en-us/library/ms646280%28VS.85%29.aspx

所以我创建了一个带有结构的联合,如下所示:

union KeyState
{
    LPARAM lparam;

    struct
    {
        unsigned nRepeatCount : 15;
        unsigned nScanCode : 8;
        unsigned nExtended : 1;
        unsigned nReserved : 4;
        unsigned nContext : 1;
        unsigned nPrev : 1;
        unsigned nTrans : 1;
    };
};

然后,当我在编辑框中收到wm_keydown消息时,我将其打印出来:

if (msg == WM_KEYDOWN)
{
    std::tstringstream ss;

    KeyState ks;
    ks.lparam = lparam;

    ss << "Key: " << (TCHAR)wparam << ", Val: " << (UINT)wparam << ", nRepeatCount: " << ks.nRepeatCount << 
        ", nScanCode: " << ks.nScanCode << ", nExtended: " << ks.nExtended << ", nReserved: " << ks.nReserved << 
        ", nContext: " << ks.nContext << ", nPrev: " << ks.nPrev << ", nTrans: " << ks.nTrans;

    SetWindowText(hOut, ss.str().c_str());
}

当我在我的编辑框中输入时我得到的值似乎不正确,有时nReserved甚至是1或0,并且nRepeatCount总是1,无论我是否按住键一起登录时间或者只需按下随机键。

我做错了什么吗?如果是这样,那么从LPARAM中获取这些值的理想方法是什么?

2 个答案:

答案 0 :(得分:12)

嗯,一方面0-15是16位,而不是15位。

答案 1 :(得分:0)

是的,容易出错(参见500的回答)。我只想使用位图和位移。

EG。 NRepeat = lparam&amp; 0xFFFF的;

相关问题