LUA: Storage
#3516
Replies: 2 comments
-
Thanks for the feedback! Yes you have to call the function But it won't directly trigger a write on storage, it just marks the data as dirty, so that you will be sure it will be saved properly when you switch to another model or when you shutdown your transmitter. The write on storage is done in the "main" task, not the "mixer" task, so there is no risk to slow down the calculations inside the mixer. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you very much, especially for finding time to respond when you're
probably busy with the new release.
…On Fri, 1 Mar 2024, 23:16 Bertrand Songis @ FrSky, ***@***.***> wrote:
Thanks for the feedback!
Yes you have to call the function dirty()
But it won't directly trigger a write on storage, it just marks the data
as dirty, so that you will be sure it will be saved properly when you
switch to another model or when you shutdown your transmitter.
The write on storage is done in the "main" task, not the "mixer" task, so
there is no risk to slow down the calculations inside the mixer.
—
Reply to this email directly, view it on GitHub
<#3516 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGQTSNUGEJMWOVGLHNSSAO3YWBWTRAVCNFSM6AAAAABEBAGW5SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DMNBSGQ4TI>
.
You are receiving this because you authored the thread.Message ID:
<FrSkyRC/ETHOS-Feedback-Community/repo-discussions/3516/comments/8642494@
github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
Porting my *TX scripts to Ethos and I have to say there are a lot of new features that I really like and believe they have great potential.
One of them is the use of storage module - for cases when I need to store some model-specific custom data (wheres in *TX I had to use raw filesystem, or a hack such as custom curve.
Since it looks like I can use storage read/writhe only in widget read/write handlers (otherwise I'm getting storage not read error), is there a way of triggering the write programmatically, i.e. one of the parameters I intend to save is changed via the code?
Is model.dirty the right call for achieving that (especially when called in flight)?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions