aethersdr / aethersdr/AetherSDR

Split: auto-off on QSY, add Split Up 1/5/10 buttons, ensure TX (not RX) slice tunes

Open
#311 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement good first issue GUI help wanted maintainer-review priority: low
Dominant language
C++
Stars
221
Forks
117
Avg merge
2d 7h
Merged PRs (30d)
299

Description

What would you like?

When changing the frequency after a split operation , it would be nice to see :

Split goes off and TX goes back to the slice which was on SPLIT

Reason : It happens ofter that one changes frequency and forgets to switch off split. Mostly on cluster based qsy or in massive switching like in WWA activities.

In my FTDX helper prog i count every frequency change of more that 2 KC as QSY and switch SPLIT off

also it would be nice to have buttons for 👍 Split up 1 , Split up 5 , Split up 10 . I have such in my FTDX helper and love that.

Another annoyance is when using split it happens often that the RX slice changes Frequency and not the TX slice. Would be nice to have different color on the Dial which is selected by the mouse and will change on wheel moves
RX frequency could/should be locked while split..only RIT makes sense.

low prio idea for enhancement

73
Harry DL9NDW

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the split-operation, QSY/frequency-change, slice-selection, and dial wheel handling in the desktop application. Review how TX and RX slices are selected during split, then verify that split auto-off, Split Up 1/5/10 controls, and TX-focused tuning behave correctly in each requested case.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.