2022-01-17 (M) EWC_Panel

I measured memory usage throughout the program by commenting out snippets, but I found that GuyverOLED used approximately 60%, and I confirmed this when I compiled an example sketch. I may switch screens, but I will finish this panel, if I can, and make a V2.0 with new hardware. For now, I cleaned up some of the code by moving print() statements to non-volatile memory and saved 14%. When I tried to print something from a two-layer array called melodies[][], my dynamic memory usage went from 78% to 118%, so I still have compatibility issues. I reduced the side of melodies[][], which freed up space. The final build will have no debugging print statements since they'll be on the MIDI line. I started a function to check if the first and last notes in a loop were compatible, but it wasn't accurate, and I was too tired to finish.
Arrangement with an inaccurate COMPATIBILITY score

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

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.