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

Provide option to preserve eeprom settings across relaunches #88

Merged
merged 1 commit into from
May 16, 2016

Conversation

peterbarker
Copy link
Contributor

No description provided.

@hamishwillee
Copy link
Contributor

So you set that value copy_eeprom or whatever =True and you get persistence, otherwise it's a fresh eeprom every time? Or to put it another way, setting copy_eeprom means "use the copied eeprom"? Or does it mean "do a copy of this eeprom and we'll load it next time". It must mean the former, but I feel a bit ambiguous.

Perhaps a name without ambiguity? use_saved_data - depending on how this actually work?

@peterbarker peterbarker force-pushed the relaunch-preserve-eeprom branch from 3b87b97 to d9aaf1f Compare May 16, 2016 00:45
@peterbarker
Copy link
Contributor Author

peterbarker commented May 16, 2016 via email

@hamishwillee
Copy link
Contributor

I like. I haven't tested this but code looks right. Merging.

@hamishwillee hamishwillee merged commit ef46bfd into master May 16, 2016
@hamishwillee
Copy link
Contributor

... and doc in readme/ command line help if not done.

@peterbarker peterbarker deleted the relaunch-preserve-eeprom branch May 19, 2016 00:17
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

Successfully merging this pull request may close these issues.

2 participants