How to deactivate unusable bands?

[R1BLH]

It is possibility to deactivate some unusable modes in the interface.
It would be nice for the same possibility for unusable bands.

[dg9vh]

I second this - but I think this would only be of sense for the logging-window and not for editing and import/export of existing adif-data. It could be possible that you import an adif (for example created by wsjt-x) where you worked on Bands you usually not operate in SSB/CW (where you log directly in cloudlog, for example).

[AndreasK79]

Then I say we need something like this:

Bands and usersettings should be stored in the database, and code updated to use the bands that are active. For awards, only the bands checked.

[dg9vh]

looks good to me...

[AndreasK79]

That was just a quick mockup. It does nothing, yet...

My thoughts:

1. A table for holding bands (band table)
2. A table holding the band information for the user (settings from the picture above) (bandxuser table)
3. Migration script to create the tables and fill
4. Fill the table (bandxuser) when creating a user
5. A view like the one above, to edit settings, create/edit/delete bands
6. Implement the band fetching all places needed (awards/qso editing/analytics?)

I think that should cover the bases. Ideas welcome.

[magicbug]

Sorry been out in a field all weekend, main thing is this is user level not global.

[AndreasK79]

Yeah, that's the idea. I'd say that I'm 40-50% done on this.

[AndreasK79]

PR #1595 is available now for those willing to test. User selectable bands can now be set on a user level. Feedback welcome.

[AndreasK79]

This is merged into station_logbooks branch.