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.

Sign up for GitHub

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

Jump to bottom

Improve frequency database default edit behavior #129

Open

kpreid opened this issue Feb 12, 2019 · 1 comment

Owner

kpreid commented Feb 12, 2019

Two silly missing features that combine to be a bad UI :

If no writable database is configured, then the user can create entries which are lost on restart. The UI should hide or disable editing options, instead.
The default configuration should include a writable database!

Also, having no UI hints at all about "which database does a record belong to" means that the writable database behavior is extra confusing.

kpreid mentioned this issue

Frequency database doesn't always load fully #127

Open

mathisono commented Feb 12, 2019

Option 2 ... I will go ahead and create a new db.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment