You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported in version: 2.0.3 Reported for operating system, platform: Windows 7, x86
Comments on the original bug report:
On 2014-08-03 18:06:24 +0000, abma wrote:
SDL created windows seems to not correctly handle the key-combination ALT+C for example. when pressing this combination, windows plays the default system sound.
On 2014-09-16 18:26:57 +0000, historic_bruno wrote:
I'm not certain this is a bug, though it is surely annoying. But for example, the same beep occurs in Visual Studio and some other window programs, when an invalid menu accelerator combo is used. Windows is quite noisy, which is why I mute all these sounds, but anyway...
I tried a quick hack in SDL to handle this message by returning MNC_CLOSE, but it had no effect, maybe I can't override this in the app? To confirm my suspicion, I removed the WS_SYSMENU style flag from SDL2's normal window style, and - no beep! but no system menu either.
Someone with more Windows API experience should look and see if something else is going wrong or if there's a good way to handle this.
On 2014-09-21 18:06:48 +0000, historic_bruno wrote:
Created attachment 1874
Handle the WM_MENUCHAR message to stop the beeping when Alt modifier key is used
On 2014-09-21 18:08:52 +0000, historic_bruno wrote:
And that led me to a solution, I wasn't constructing the LRESULT properly in my last test. The attached patch stops the beep in an SDL window when Alt+[key] is used. One thing I still notice is the mouse cursor briefly flickers to the default cursor from my application's custom one, which occurred before the patch and may be related.
On 2015-01-02 16:16:09 +0000, abma wrote:
patch works for me, i'll get (hopefully) some more feedback from
I still notice is the mouse cursor briefly flickers to the default cursor from my application's custom one, which occurred before the patch and may be related.
this happens for me, too but it happened already before the patch, so no big deal. but thats imo a slightly different bug.
the beep seems fixed by this patch, others verified that, too. thanks for helping!
On 2015-01-24 03:21:05 +0000, wrote:
The correct fix for this is to handle the WM_SYSCOMMAND SC_KEYMENU and return similar to how SDL2 currently eats SC_SCREENSAVE / SC_MONITORPOWER
On 2015-04-07 04:57:53 +0000, Ryan C. Gordon wrote:
(sorry if you get a lot of copies of this email, I'm marking several bugs at once)
Marking bugs for the (mostly) final 2.0.4 TODO list. This means we're hoping to resolve this bug before 2.0.4 ships if possible. In a perfect world, the open bug count with the target-2.0.4 keyword is zero when we ship.
(Note that closing a bug report as WONTFIX, INVALID or WORKSFORME might still happen.)
--ryan.
On 2015-05-26 15:09:34 +0000, Ryan C. Gordon wrote:
This bug report was migrated from our old Bugzilla tracker.
These attachments are available in the static archive:
Handle the WM_MENUCHAR message to stop the beeping when Alt modifier key is used (SDL_windowsevents.c.diff, text/plain, 2014-09-21 18:06:48 +0000, 406 bytes)Reported in version: 2.0.3
Reported for operating system, platform: Windows 7, x86
Comments on the original bug report:
On 2014-08-03 18:06:24 +0000, abma wrote:
On 2014-08-03 18:06:54 +0000, abma wrote:
On 2014-08-03 20:15:54 +0000, abma wrote:
On 2014-08-04 23:26:16 +0000, abma wrote:
On 2014-08-04 23:41:20 +0000, abma wrote:
On 2014-09-16 18:26:57 +0000, historic_bruno wrote:
On 2014-09-21 18:06:48 +0000, historic_bruno wrote:
On 2014-09-21 18:08:52 +0000, historic_bruno wrote:
On 2015-01-02 16:16:09 +0000, abma wrote:
On 2015-01-12 04:30:25 +0000, abma wrote:
On 2015-01-24 03:21:05 +0000, wrote:
On 2015-02-20 04:48:38 +0000, historic_bruno wrote:
On 2015-02-22 15:04:21 +0000, wrote:
On 2015-02-22 20:31:37 +0000, historic_bruno wrote:
On 2015-04-07 04:57:53 +0000, Ryan C. Gordon wrote:
On 2015-05-26 15:09:34 +0000, Ryan C. Gordon wrote:
The text was updated successfully, but these errors were encountered: