2024-12-31 (Tu) EWC_Noodle Ham-Fisted Chording

I could fit a second play mode, which I called Ham-Fisted Chording. The button pressing looked like binary code but was simpler at the cost of getting fewer combinations. The advantage is that you never have to press more than three buttons, and they are always adjacent. Five buttons only had 12 combinations, but that was exactly how many I wanted since twelve semitones were in an octave. I arranged the code to only play the most drastic combination, and any extra buttons get ignored. It would only register the top three if someone pressed all five buttons.

I looked at my previous code, which only supported a single button, and saw some repeated code, so I removed it to save some memory. Of course, I introduced many new problems and did not save significant memory, but I debugged the latest problems and copied the applicable code into the Ham-Fisted mode. The new mode had twelve if() statements arranged by complexity. Each check looked for specific key combinations and ignored any previous matches. When I locked down the revised code for each mode, I played each to verify that they worked.

Ham-Fisted mode

GitHub repo for EWC_Noodle.

The rest of the posts for this project have been arranged by date.
First time here?

Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11

Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by  Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.
2024-12-29