Saving config: performance and usability

[asterics]

Saving config: performance and usability

[ChrisVeigl]

changing AT SA so that it overwrites the slot data in EEPROM is not trivial and would need some changes in the eeprom implementation (move all remaining data if the slot size changes), see also discussion in
#46

we could discuss several strategies:

• improve the speed of EEPROM access and implement the defragmentation / slot copy function
• store keystings seperately so that less data must be copied on demand
• store slot data in ESP32 flash (if BT-AddOn is available)
• use a fixed slot size (reserve memory for max keystring length) - is would be fast and easy, but is wasteful (and no option for the much smaller EEPROM in the FABI system / AVR)

[ChrisVeigl]

a first version of EEPROM slot copy is there:
8f36024
although it should work in theory and the EEPROM bin/block writes improve performance, this needs further consideration ...
I think it is not reasonable to save (and respectively change EEPROM content) every time a user makes small changes in the FlipMouse configuration.

[ChrisVeigl]

further worked on that, see 27696be

Using EEPROM page writes and optimized I2C buffer size, a slot save can now be performed at 1/3 of the time, and moving slots (in course of the save action) is 10 times faster. Example timing for moving three slots and then overwriting a slot: ~580 ms.

Please note that the C# GUI in this branch now performs the AT SA action when pressing the "Test Settings" button, and that basic debug messages are turned on in the firmware.

[klues]

sounds great! 👍
Sorry for my naive thought that AT SA was just lacking of a single else statement 😉

[benjaminaigner]

With all the last commits on v2 and the ongoing work on v3 with the RP2040 branch, we can close this issue.