¿ªÔÆÌåÓý

Re: sbitx laggy because it writes user settings way too often #sBitx


 

I think the intent of the code was to only write 30 seconds after the last tuning update, it just wasn't coded correctly.

I'm not sure using a swap file or tmpfs will change things too much because I think the intent is to have settings to use the next time the radio starts rather than having a database for other parts of the code to access in real time.? Other parts of the code access the in-memory data not the on-disk data.

I think after fixing the coding error the logic will be okay, it's now just a matter of asking people what their expectations are about how often to write to disk vs what kind of data retention they have.? If they change the dials then shut down the radio immediately or the sbitx app crashes, any changed settings will be lost.? I guess that's not the end of the world so maybe keeping the logic set for 30 seconds is OK.

Actually that raises another point,? I don't see the code writing the settings back to disk when the app is closed, so you lose any changes you make in the 30 seconds preceding app shutdown.

--
Regards,
Dave, N1AI

Join [email protected] to automatically receive all group messages.