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 we embedd the enabled features into the .apj or into the hwdef in rom or something.? #10

Open
davidbuzz opened this issue Aug 17, 2021 · 3 comments

Comments

@davidbuzz
Copy link

No description provided.

@shiv-tyagi
Copy link
Collaborator

Hey @davidbuzz! Can you please elaborate more? Where are you planning to use that information if we somehow make it happen?

@davidbuzz
Copy link
Author

davidbuzz commented Mar 16, 2025

scenario:
1 - user makes a custom-build for their flight controller, uses it, finds it vauable.
2 - a lot of time pases, say its a year later.
3 - user re-visits in the future , having completely forgot what options they used to buuild it the first-time.
4 - user cant remember what buld-options were used, wouldnt it be nice if that was stored-away-someplace-safe (eg a .txt file IN rom ) so they could download it and re-use the same settings,?

@rmackay9
Copy link

rmackay9 commented Mar 17, 2025

A simpler solution might be to add "Save config", "Load config" buttons to the left of the "Reset feature defaults" that allows a user to save/load the checked features. In case the user tries to load a config generated using an older version of the build server where some features were not present, the load button would just use the defaults

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

3 participants