If I use #DEFAULT_NONVOLATILE in a simpl+ program does it have the same quirks as using a Ram in simple windows?
IE: if the position of the created module gets moved during programming changes the next reboot will likely have the wrong Ram contents being referenced?
Posted Nov 2, 2021, 8:24 PM UTC
It's not clear what you need it for but if it's for light scenes, I've been using CCI JSON suite lately instead of RAM to get around this. I just write when there's changes and read on startup. I hold all the scene values behind buffers and "release" the right one when recall is pressed. Similar for sensor, timer & astro offset settings but without the buffers.
Not so much this modules position in the symbol tree as it is this modules position relative to other things that use the nonvolatile storage in the symbol tree.
Read and write to file if its an issue, or use a singular ram symbol and/or only put things that use NVRAM at the top of your tree, and never move the position.
Yeah. Try it and see. I will say, though that managing stuff in NVRAM via S+ uses up much less NVRAM than in Simpl.