Windows raw input - problem with arrow keys

Here's how I use raw input in my game:




// Get the standard/unbuffered raw input data
if(::GetRawInputData(hRawInput, RID_INPUT, &m_oRawInput, &m_uiRawInputSize, sizeof(RAWINPUTHEADER)) != static_cast<UINT>(-1))
{
// Raw input from keyboard
if(m_oRawInput.header.dwType == RIM_TYPEKEYBOARD)
{
switch(m_oRawInput.data.keyboard.Message)
{
case WM_KEYDOWN:
switch(m_oRawInput.data.keyboard.VKey) // Virtual key
{
case VK_ESCAPE: // Escape key
onEscapeKeyDown();
break;

case VK_PAUSE: // Game_Mode_Paused key
case 'p':
case 'P':
onPauseKeyDown();
break;

case VK_PRINT: // Print key
onPrintKeyDown();
break;

case VK_LSHIFT: // Left-shift key
onLeftShiftKeyDown();
break;

case VK_RSHIFT: // Right-shift key
onRightShiftKeyDown();
break;

case VK_LCONTROL: // Left-control key
onLeftControlKeyDown();
break;

case VK_RCONTROL: // Right-control key
onRightControlKeyDown();
break;

case VK_UP: // Up key
onUpKeyDown();
break;

case VK_DOWN: // Down key
onDownKeyDown();
break;

case VK_LEFT: // Left key
onLeftKeyDown();
break;

case VK_RIGHT: // Right key
onRightKeyDown();
break;

case VK_RETURN: // Enter key
onEnterKeyDown();
break;
}
break;

case WM_KEYUP: // Key up
break;
}
}



I'm using windows raw input in order to handle keyboard and mouse. I heard it's recommend way of getting it...
[/quote]
The recommended way of detecting keyboard and mouse input is using Windows messages.

I'm also suspicious of how you are using the buffer. The first call is to get the size of the buffer, which you do not use. Then you pass a 41 byte buffer in, but you pass SizeOfBuffer again, indicating that your buffer is SizeOfBuffer bytes long.

I'm using windows raw input in order to handle keyboard and mouse. I heard it's recommend way of getting it...

The recommended way of detecting keyboard and mouse input is using Windows messages.[/quote]
This.

Raw input is fairly complicated, and you should only really be using it if you require high DPI mouse input (E.g. a first person shooter style game)

I'm also suspicious of how you are using the buffer. The first call is to get the size of the buffer, which you do not use. Then you pass a 41 byte buffer in, but you pass SizeOfBuffer again, indicating that your buffer is SizeOfBuffer bytes long.

yea well firstly I'm loading required size of data to SizeOfBuffer and then I pass all these data to Buffer. Buffer has 41 size becouse I read at toymaker that 32 is needed for mouse and 40 for keyboard and so while passing the data some places in Buffer might be empty(for example if mouse is read) and that isn't that bad solution I hope.
The problem is that when I push the arrow (right for example) my character in game moves to right but when I quickly push right second time it is supposed to run right but it doesn't. If I change to another key(not arrow one) everything works fine... ;/

Thanks a lot for everyone who posted
hmm It seems I solved the problem. I don't know why but after the arrow key is released it sends me "255" virtual code and that's why the data was wrongly placed in my array. What I've done is restrict receiving keyboard input: only if the virtual key != 255