We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 712 - Arrow keys seems to be not intercepted in Windows Vista
Summary: Arrow keys seems to be not intercepted in Windows Vista
Status: RESOLVED DUPLICATE of bug 743
Alias: None
Product: SDL
Classification: Unclassified
Component: events (show other bugs)
Version: HG 2.0
Hardware: x86 Windows Vista
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL: http://freya3d.co.cc
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-06 04:50 UTC by Dmitri Vedenko
Modified: 2009-09-26 03:09 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitri Vedenko 2009-03-06 04:50:53 UTC
Hello, I'm using 4454 revision of SDL, and I experience the following strange behavior. On Windows Vista SP1 (library and code are compiled using MSVS 2005 Professional) SDL seems to not intercept events connected with arrow buttons (still code works perfectly on Linux (x86) and Mac Os X 10.5.6).

I am using the following code Uint8* state = SDL_GetKeyboardState(NULL); to fetch the keyboard state snapshot and I properly update SDL event queue. As far as I can see, all other keys work perfectly
Comment 1 Dmitri Vedenko 2009-03-08 00:46:32 UTC
Tests under Windows XP SP2 shown the same problem
Comment 2 Derek Kulinski 2009-08-22 12:55:58 UTC
(In reply to comment #1)
> Tests under Windows XP SP2 shown the same problem

Do you call SDL_PumpEvents() before using SDL_GetKeyboardState()?

I have problem with key handling but SDL_GetKeyboardState() works for me on Vista.
Comment 3 Derek Kulinski 2009-08-22 12:57:28 UTC
Actually looks like you're referring to SVN version, I'm using stable. Sorry.
I guess I can't delete my last post.
Comment 4 Sam Lantinga 2009-09-26 03:09:53 UTC

*** This bug has been marked as a duplicate of bug 743 ***