Acid Curds chord storage vs. Enigma TM storage
Opened this issue · 1 comments
I've realized that since the user_chords array (in GlobalSettings) was replaced with user_turing_machines in Hemisphere, chord progression sequences made in the Acid Curds app are not properly saved in EEPROM. The app still works, and most other settings are saved, just not the selected chords.
This bug applies only to the Phazerville fork.
One potential solution to this that I'm considering is for Acid Curds to take precedence when enabled, and simply replace user_turing_machines with user_chords in that case - they both use the same block of 160 bytes. This seems like a good compromise for Custom Builds, but it will also apply to the Teensy 4.x builds with all the apps - Enigma won't be able to recall any of its TuringMachine's if Acid Curds is present. This issue will go away someday if I implement LittleFS or SD card storage for more space on Teensy 4.x.
Do more people care about saving Chord Progressions? or a library of Turing Machines?
An alternate solution is to store user_chords with the rest of Acid Curds' app data, but that will overflow EEPROM on Teensy 4.0. We just can't have it all, folks.