everytime I do a save() on my Espruino board, the set button handler is triggered with weird data.
Is there a reason for that? Is there anything in the data that can be used to ignore that after-save trigger?
That's odd. I've just made a new bug for it - I'm not sure entirely why but my guess is it's actually some issue with removing the watches on deinitialisation. It looks to me like it doesn't happen if you hard reset - it's only when you call save() or load()
Hard reset (and load() as far as I remember) work fine. Hard reset was my work around for the time being.
Follow-up: a sequence of reset() and load() works fine, too.
Don't worry about formatting, just type in the text and we'll take care of making sense of it. We will auto-convert links, and if you put asterisks around words we will make them bold.
For a full reference visit the Markdown syntax.
© Espruino, powered by microcosm.
Report a problem