Closed jackiew1 closed 4 years ago
Thanks for testing this. I'll look into the issue later this week.
I just realized what the issue is. Since #47, NM updates menu items when the config changes, but that's only detected the first time it's checked (i.e. it will update the first menu after the change, but leave the other one as-is). To fix this, I'll either need to store the current revision with an incrementing counter (which is stored as a property on the menu), or store which menus were updated each time.
I haven't tried this, but I think a simpler way to reproduce this issue would be to open the reader menu, go home and connect over USB, make a config file change which changes a reader menu item, open the main menu, then open that item from the reader menu again.
Update: I tried it, and it's slightly more complex to reproduce the issue than that. It only works the other way around since the reader menu gets regenerated every time a new book is opened. To reproduce the issue, the config must be changed, then the reader menu must be the first to be pressed, then go back to the home screen and open an old menu item from there.
You asked for some testing feedback so here's mine.
Good news: I only have simple menu options. Everything I want is now working OK.
Not-so-good news: During my testing (on a KA1) I did have a problem which I was able to reproduce several times.
This is my config file:
These were the steps to reproduce the problem using the above config:
* USBconnect
* Screenshots on
> Home
* Rescan books
just to prove the screenshot exists.At this point the KA1 freezes and reboots. After this everything is OK.
I don't know if this is any help but this stack log was created: