Saving Problem in the preset description / Waveshare 4.3B v.2.0.1.2

[65Timo]

After updating to Waveshare 4.3B (v2.0.1.2), I have the following problem:
If I enter multiple spaces in a row in the preset description, the entire text isn't saved. After changing presets, the text field is empty again.
If I avoid using multiple spaces in a row, saving works perfectly.

[Builty]

Thanks for the report. I'll check it out.

[Builty]

I ran a test, but for me it saved OK even with multiple spaces.
Some users have ran into config saving issues, as the structure had to changed.

I think its worth trying a full Erase with the programming software, and then flash as normal. This will clear out all config and make a fresh copy. Hopefully that solves it.

[50pln]

I don't know what's going on, but I can't save the settings in the BT section. It doesn't restart or respond to the button. Is it just me? I wanted to deactivate BT. 4.3B

[Builty]

Maybe try resfreshing the web page. Particularly after a firmware update, as the web broswer may be caching the old page.
Failing that, the full erase mentioned above is worth a shot, however that issue usually has different symptoms to this.

[50pln]

It doesn't work on three PC browsers, plus the incognito versions, and on my phone as well. It works fine on W.Zero, so it's probably not the browsers' fault. Save and Reboot only works in the WiFi section; unfortunately, it doesn't work anywhere else.

I also changed the mDNS Name to treat it as a new site and nothing.

I'll erase everything and we'll see this again.

[50pln]

And it works, folks!!! :) Erasing everything and re-flashing it fixed all the issues. Thanks.

[65Timo]

Hello, a few weeks ago I described my problem with saving the text field in this chat (see above).
I've reinstalled the latest version. Of course, I also completely cleared the cache beforehand.

The problem persists even with the latest beta version.
As a reminder, this problem didn't exist with the older 1.xxx versions.

To illustrate the error, I'm uploading a short video for you.
Please watch this video to the end; you'll then see this saving issue.

Thank you in advance, and I'm very curious if you have any ideas about this.

Best regards, Sigi

Video: https://github.com/user-attachments/assets/b583d981-529a-482e-bb92-5022373154be

[Builty]

Hi. Thanks for the report. I would not have tested that kind of sequence before.
I can see that in your test, it starts going bad when the text length is around 30 characters, which makes sense as in the latest code the max length of this text is 32 bytes (31 characters plus 1 null terminator character.)
It used to be longer, but I had to cut it down shorter to allow for the extra storage space required by the big Tonex pedal having 150 presets.

I would say there is a bug here that is not properly handling things when the text exceeds the maximum. I have noted it to fix.
As a work-around, if you keep the text to 31 or less characters, it should be OK