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 information about the width, display, and order of header fields be saved locally? #197

Closed
kidzgy opened this issue Apr 30, 2024 · 4 comments
Labels
fix-committed Fix for the issue is in the main branch wishlist Low priority nice to have features

Comments

@kidzgy
Copy link

kidzgy commented Apr 30, 2024

Can information about the width, display, and order of header fields be saved locally?

Currently, the configuration information such as the width and order of the header for "Name" and "Speed" is saved in the browser cache, so if you change the browser, you have to reset the configuration information, which is very troublesome, and it is not interoperable with the exe program.

Is it possible to add an option to save these table header configuration information locally instead of the browser cache, in this case, no matter how to change the browser to clear the cache or even use the exe, this information can be saved without having to reconfigure.

Thanks!

@qu1ck qu1ck added the wishlist Low priority nice to have features label Apr 30, 2024
@qu1ck
Copy link
Member

qu1ck commented Apr 30, 2024

Yes, settings export/import can be added. Though I should be careful on how config versioning would work. Until now I only cared about newer version extending old config, with export/import I need to consider how older version will overwrite/merge with newer one as well.

@kidzgy
Copy link
Author

kidzgy commented Apr 30, 2024

I think we can discard the idea that the new version is compatible with the old version, which is still saved in the browser cache, while the new version can only support configuration import and export and the ability to check whether to save locally or not.

With a major version update like this, reconfiguration is necessary. Thankfully, the first reconfiguration doesn't take much time, but the convenience of using the exe as well as the web in subsequent versions is greatly enhanced.

@qu1ck
Copy link
Member

qu1ck commented Apr 30, 2024

It's not relevant now but when the new version will become old version then it will be.

qu1ck added a commit that referenced this issue Jun 9, 2024
@qu1ck qu1ck added the fix-committed Fix for the issue is in the main branch label Jun 9, 2024
@qu1ck
Copy link
Member

qu1ck commented Oct 9, 2024

Added in v1.4.0

@qu1ck qu1ck closed this as completed Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix-committed Fix for the issue is in the main branch wishlist Low priority nice to have features
Projects
None yet
Development

No branches or pull requests

2 participants