Skip to content
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.

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

NAQP - dx stations are not included in simulation #353

Open
1 task
w7sst opened this issue Sep 18, 2024 · 1 comment
Open
1 task

NAQP - dx stations are not included in simulation #353

w7sst opened this issue Sep 18, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@w7sst
Copy link
Owner

w7sst commented Sep 18, 2024

Description

During a NAQP Contest simulation, the DX stations in the call history file are not included in the simulation. They should be.

Steps To Reproduce

  1. This is hard to reproduce without debug code. Debug code exists to filter/load only DX stations.
  2. Select NAQP Contest
  3. Notice that none are included

Expected behavior

  • DX stations within the call history file should be included and randomly appear during the simulation.
  • When working a DX Station, the sending DX station only sends their Name, they do not send their State/Prov/Entity. When entering the exchange information, the State field will be left blank. ESM (Enter sends Message) should work for this case by allowing a blank Exch2 field. There are currently problems with this.

Actual Behavior

  • The DX Stations are not included in the simulation.
  • When the are included (using debug code to select only DX stations), other problems are encountered with the Enter key (ESM) behavior.

Reproduces how often

100%

Version information

  • Morse Runner version: 1.85-rc1, and probably prior versions as well.

Tasks

  • Yes, I'm available to help test a solution to this problem.
@w7sst w7sst added the bug Something isn't working label Sep 18, 2024
@w7sst w7sst self-assigned this Sep 18, 2024
w7sst added a commit that referenced this issue Sep 20, 2024
@w7sst
Copy link
Owner Author

w7sst commented Dec 20, 2024

I notice that the call history file contains ~1% international callsigns. Thus, this issue is of lower priority for now. I considered trying to fix this for the 1.85.2 release, but decided to defer it until later.

@w7sst w7sst added this to the v1.85.2 - bug fix release milestone Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant