Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't change auto export frequency and export suggestion #368

Open
Sree-Siddhaarth opened this issue Feb 23, 2024 · 3 comments
Open

can't change auto export frequency and export suggestion #368

Sree-Siddhaarth opened this issue Feb 23, 2024 · 3 comments

Comments

@Sree-Siddhaarth
Copy link

Currently csTimer has the autoexport frequency set to 100. It would be better if it is changable. I prefer to have it export every 20 or 25 solves.

One more thing. Having able to specify the folder where the csTimer backup happen on both google drive and "export to file" would make it much easier for future recovery.

@afedotov
Copy link
Contributor

Actually ability to set autoexport frequency is already done, but option is currently hidden under DEBUG flag. Maybe just expose this to the users? And slightly extend option list to be more granular.

kernel.regProp('kernel', 'atexpi', ~1, 'Auto Export Interval (Solves)', [100, [50, 100, 200, 500], ['50', '100', '200', '500']]);

@cs0x7f
Copy link
Owner

cs0x7f commented Feb 24, 2024

I am not planning to open this option at the moment. I think the current setting of 100 solves should be a relatively safe value. If it were changed to be smaller (or users were allowed to change it), the pressure on the server would become greater.

@Val-kaden
Copy link

Val-kaden commented Mar 4, 2024

@cs0x7f you're right but restricting that option to only the user's storage would not increase the stress on the servers right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants