- Split DirectInput keyboard handling into a separate file and class. I also
switched it to buffered input, and the pause key seems to be properly cooked, so I don't need to look for it with WM_KEYDOWN/UP. Tab doesn't need to be special-cased either, because buffered input never passes on the Tab key when you press Alt+Tab. I have no idea why I special-cased Num Lock, but it seems to be working fine. By setting the exclusive mode to background, I can also avoid special code for releasing all keys when the window loses focus, because I'll still receive those events while the window is in the background. SVN r1613 (trunk)
This commit is contained in:
parent
0a310b9832
commit
7fea07dff7
9 changed files with 350 additions and 163 deletions
|
|
@ -762,7 +762,6 @@ void FDInputMouse::ProcessInput()
|
|||
DIDEVICEOBJECTDATA od;
|
||||
DWORD dwElements;
|
||||
HRESULT hr;
|
||||
int count = 0;
|
||||
int dx, dy;
|
||||
|
||||
dx = 0;
|
||||
|
|
@ -787,8 +786,6 @@ void FDInputMouse::ProcessInput()
|
|||
if (FAILED(hr) || !dwElements)
|
||||
break;
|
||||
|
||||
count++;
|
||||
|
||||
/* Look at the element to see what happened */
|
||||
// GCC does not like putting the DIMOFS_ macros in case statements,
|
||||
// so use ifs instead.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue