I am finding that the longer I hold down a button the longer it takes to recognize that it has been released.
I put log statements into OnButtonDown and OnButtonUp and can see that OnButtonUp is not called for a number of seconds in some cases. But when just clicking the button both statements are logged effectively immediately.
Notably, I am finding there to be a correlation between how much processing is occuring in OnNextFrame and the "Up" response. If I comment out all code in OnNextFrame then the problem effectively disappears.
I would expect that regardless of how long the frame processing takes, the next iteration would catch that the button has been released, but instead I can see many frames continue to be processed before the input event is handled.
Obviously I require the "Up" event to be handled immediately. Is there anything obvious that would explain this behaviour?
I should add that this is occurring on a Dell Axim x51v (VGA) running at 624mhz and does NOT happen while testing on the WM5 Pocket PC VGA emulator image for VS2005 on Vista.