Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PRINT (Print Screen) key event #39

Closed
SDLBugzilla opened this issue Feb 10, 2021 · 0 comments
Closed

PRINT (Print Screen) key event #39

SDLBugzilla opened this issue Feb 10, 2021 · 0 comments

Comments

@SDLBugzilla
Copy link
Collaborator

This bug report was migrated from our old Bugzilla tracker.

Reported in version: don't know
Reported for operating system, platform: Windows (All), x86

Comments on the original bug report:

On 2006-01-31 11:26:09 +0000, Sam Lantinga wrote:

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:

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

On 2006-03-14 02:06:14 +0000, Sam Lantinga wrote:

This is fixed in CVS.
madebr pushed a commit to madebr/SDL that referenced this issue Mar 19, 2023
@philippemnoel
on cmd+q exit, set a flag in the SDL_QuitEvent struct (libsdl-org#39)
1fb34f3 
* on cmd+q exit, set a flag in the SDL_QuitEvent struct

* add cmd+q change to the changelog

Co-authored-by: Philippe Noël <21990816+philippemnoel@users.noreply.github.com>
Wohlstand pushed a commit to Wohlstand/SDL that referenced this issue Mar 21, 2024
@mardy
Implement rendering of mouse cursors (libsdl-org#39)
cfd4ce3 
* ogc: use unsmoothed coordinated from WPAD IR

For some reason the smoothed coordinates are not available on the top
left corder area of the screen. The normal coordinates work fine,
instead.

* ogc: implement rendering of mouse cursor

The cursor is drawn (if it needs to) at the end of each frame, right
before copying the changes to the EFB.

The small change in SDL_render_ogc.c is needed because we need a
specific blending mode to draw the cursor, and the renderer will need to
reset it.

The SDL_ogccursors.h file contains bitmaps of cursors to use on the Wii.
The hand drawing is taken from
https://wiibrew.org/wiki/Wii_Homebrew_Cursors (all cursors there are
under public domain), the arrow cursor has been created by me in
inkscape. The files then have been exported in GIMP as C source file and
their data pasted into this file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SDLBugzilla