Request: Customize Column Headers

[fmk2]

I just recently moved, after more than 20 years, from Windows and HRD to Linux and QLog. So far, I have to say that QLog is fantastic!

That said, one nice feature would be the ability to customize the column header names in the logbook. A couple good examples are the Clublog Upload Date and Clublog Upload State. I use one or both of these fields to ensure that a QSO was successfully uploaded to Clublog, but the column takes up a lot of screen real estate because of the title. I can shrink the width of the column of course, but then it can be difficult to tell if I'm look at (for example) Clublog Upload State or LoTW Upload State (which I also use). I'd like to be able to rename those columns to something like 'CL Date' and 'CL State' to save screen space.

The back end names for these columns, which of course must comply with the ADIF standard, need not change. It would just be an option for the user to rename what is shown on their screen.

N6OI

[foldynl]

I’ve mentioned several times that QLog follows a minimalistic approach wherever possible. I don’t like applications where absolutely everything can be configured and the developer essentially leaves all decisions to the user. Instead, I try to find ways for the default settings to work well for as many users as possible.

I understand what you're asking for, but imagine what your request would means. It would require a mapping table of names to new names. The ADIF specification contains over 150 fields, and more are added every year; this is also the policy of the ADIF committee, because according to one of its members, he’d even support logging "shoe size" if there were interest. So you can imagine how frustrating such a mapping table would be for users.

Shortening names might be the right direction, but "CL" is not an appropriate abbreviation. Why? Because it could mean Cloudlog or Clublog. I think this would be more confusing for users than having a few extra pixels when displaying the full service name. Don’t you think?

[fmk2]

I definitely agree that too much user customization is a bad thing... it can be virtually impossible to support from the developer's standpoint (I've been there). But I also think that a column header like 'Clublog Upload State' for a column that is just a boolean value is unnecessarily long, and makes displaying the column in the UI somewhat impractical given that screen real estate is limited.

And yes, "CL" is not an appropriate abbreviation, but I was just using that as an example, not a suggestion.

You might be able to avoid the addition of a mapping table if the user was able to overwrite the display value directly. You have the ADIF name as the key value, so what is displayed on the user's screen is somewhat irrelevant. But I also understand that it could complicate support from the standpoint that users would tend to ask questions or request support based on whatever they had set the display name to rather than referencing the ADIF name... so perhaps that isn't practical either.

Thanks for considering the idea, and taking the time to respond.