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.

Date: Wed, 04 Jan 2006 22:20:12 +0100
From: Manuel Bilderbeek <manuel@msxnet.org>
To: sdl@libsdl.org
Subject: [SDL] PRINT (Print Screen) key event and full screen problems in wind
-- Message: 19392   --  Next: 19393   ----------------------------------------
Hello all,

For our SDL-powered MSX emulator (openMSX), we use a key binding to the
print-screen key (SDLK_PRINT). This works fine on e.g. Linux, but not in
Windows. Here's some quotes from durnew on IRC:

<durnew> windows only reports print screen on KEYUP
<durnew> not KEYDOWN
<durnew> not certain how to fix that, other than document it
<durnew> Diablo-D3: well, the directx driver requires a different fix
<durnew> as it doesn't have a scancode for print screen               
<durnew> i've been trying to figure out what the deal was!         
<durnew> but atleast i've located the issues :)
<durnew> ah, well, both drivers were broken anyway!             
<durnew> neither one of them is fixable
<durnew> without rewriting half the library
<durnew> which i imagine, is why they aren't fixed!
<durnew> the windib driver issue can be half fixed :\                  
<durnew> Quibus: windib only reports that scancode on KEYUP and directx 
only contains a SYSRQ binding, SDL would have to give both SDLK_PRINT
and SDLK_SYSREQ the same values

Is there really nothing that could be done to get this working better
(or actually: working at all) in Windows?

The only way we could hack it into the windx driver, is to replace the
binding to SYSREQ with a binding to PRINT.... But that's not a good
solution of course.
Oh, and isn't this just a bug? If so, and if it's not yet in the
bugzilla, can someone please add it?