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

Opening cw keyboard causes sbitx to exit #79

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

sbeckman
Copy link
Contributor

This proposed change prevents the sbitx app from exiting when the CW keyboard is opened.

Fix for high CPU usage and audio dropouts. Includes a define to enable debugging messages.
Changed the level of rigor from FFTW_ESTIMATE to FFTW_MEASURE in order to resolve an issue where the FFTW library would sometime make a bad choice about the FFT algorithm to use.

Added support for Wisdom files so that the FFTW library does not have to spend time picking the algorithm.
Changed the level of rigor from FFTW_ESTIMATE to FFTW_MEASURE in order to resolve an issue where the FFTW library would sometimes make a bad choice about the FFT algorithm to use.

Added support for Wisdom files so that the FFTW library does not have to spend time picking the algorithm.
If the screen height is set to 425 or less pixels, then when the CW keyboard is opened, the sbitx application crashes. This occurs because the calculated screen height of the waterfall becomes a negative number. That height is used in a malloc() call near line 1523 in sbitx_gtk.c Obviously the malloc() call does not work well with a negative number, so it fails, and sbitx exits.
This change prevents the waterfall area from having a height less than 0, which in turn prevents the malloc() call from failing.
@n1ai
Copy link
Contributor

n1ai commented Jan 20, 2024

As your commit history shows and as I have verified, all that is needed relative to the current HEAD of main is the last commit ( a577fd1 ). IMO the other stuff may cause trouble later. Ideally we'd have a PR with just one commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants