keypress events cause unavoidable beep sound with wxagg

[briantoby]

Bug report

Bug summary

Pressing a key in a MPL plot causes a beep. This is not a serious problem, but is annoying.

Code for reproduction

use the code here https://matplotlib.org/stable/gallery/event_handling/keypress_demo.html, but add

import matplotlib
matplotlib.use('wxAgg')

Actual outcome

Every time a key is pressed, I hear a bell sound (a beep).

Expected outcome

I should be able to eliminate this using this in the callback:

def on_press(event):
    event.guiEvent.Skip(False)
    ...

The reason for this is in this callback handler in backend_wx.py

    def _onKeyDown(self, event):
        """Capture key press."""
        key = self._get_key(event)
        FigureCanvasBase.key_press_event(self, key, guiEvent=event)
        if self:
            event.Skip()

Since the method ends with event.Skip() (same as event.Skip(True)) the call to event.guiEvent.Skip(False) is ignored.
If this is rewritten as:

    def _onKeyDown(self, event):
        """Capture key press."""
        if self:
            event.Skip()
        key = self._get_key(event)
        FigureCanvasBase.key_press_event(self, key, guiEvent=event)

Then existing code will function as before, but there is the option to suppress the beep. One could argue that .Skip(False) should be the default, but that would be a change in how MPL functions.

Matplotlib version

• Operating system: MacOS 10.15.7
• Matplotlib version: 3.3.2
• Matplotlib backend: MacOSX
• Python version: 3.9.1
• Jupyter version: N/A
• Other libraries: wxpython 4.1.1

default conda channels except wxpython from pypi.

[github-actions]

This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!

[briantoby]

I have not confirmed that the bug still exists, but looking at the current wx backend code, I don't think at present this issue has been addressed.