Mesh data not saved after autolevel

[ritchiedc]

Description

The mesh data is not saved to "eeprom" after an autolevel initiated from the screen.

Steps to Reproduce

1. Reset factory settings
2. Execute "M420 V" -> invalid mesh
3. Execute autolevel from screen
4. Execute "M420 V" -> valid mesh data
5. Cycle power
6. Execute "M420 V" -> Invalid mesh

Expected behavior: Mesh data should be saved thru power cycles

Actual behavior: Mesh data is lost after power cycle

Additional Information

As a work around, changing the z offset after an autolevel will cause the equivalent of an M500 resulting in parameters being saved, including any changes to esteps (M92 Exxx) and Fade Height (M420 Zxx).

[ritchiedc]

In Creality's original code a call to "settings.save()" is made in G29.cpp at line 853. This is missing from G29.cpp at line 768. To avoid having to include "settings.h" in G29.cpp the call to settings.save() can be added to the DWINTouch_bedlevel_finish_callback().

Edit: If you want the screen initiated autolevel to save but the G29 command from something like Octoprint to not save and require an M500 put the settings.save() call inside the check for 3 == waitway in the callback function.