Skip to content

Mixing modes with submodes #798

Description

@jholubinka

Feature Description

Hi @foldynl,

I'm a new user of QLog and I want to start by thanking you for the effort you've put into developing and maintaining the application. It's a solid and promising tool for amateur radio logging.

While using QLog, I noticed that it follows the ADIF specification very closely, which is absolutely correct. However, this strict implementation can sometimes negatively affect the user experience. For example, FT8 is shown as a mode, while FT4 appears as a submode under MFSK. This results in uneven column usage in the main log view (there's need for two columns, and on small screens the space is precious) and can be visually inconsistent.


Suggested Improvements

1. Unified Mode/Submode Display (Optional UI Feature)

  • Add a configuration option that allows users to use **merged mode/submode ** in the app.
    • If a submode is present, display it.
    • If not, fall back to displaying the mode.
    • Optionally, allow a combined format like MFSK/FT4 or just FT4, depending on user preference.
  • This could be implemented as an additional column in the list, leaving the existing mode and submode columns untouched.

2. Simplified Mode Selection UI

  • Replace the current separate mode and submode combo-boxes with a single unified selector that lists all items (e.g., "FT8", "FT4", "RTTY", etc.).
  • This would make the logging process more intuitive.

Important Notes

  • These changes should be purely cosmetic and UI-level only.
  • All internal logic, including ADIF export and data filtering, should remain unchanged to preserve compatibility and data integrity.

Thanks again for your work on QLog! I hope this suggestion aligns with your vision and helps improve usability for others as well. I'm happy to help test or provide feedback if needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    Status
    Done - branch: testing_0.51

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions