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.

Sign up for GitHub

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

Jump to bottom

Call History #121

Closed
py4xx opened this issue Jul 26, 2024 · 14 comments · Fixed by #209
Closed

Call History #121

py4xx opened this issue Jul 26, 2024 · 14 comments · Fixed by #209
Assignees
@mbridak
Labels
enhancement New feature or request

Comments

@py4xx
Copy link

py4xx commented Jul 26, 2024

Is your feature request related to a problem? Please describe.
Using call History helps a lot in the competition.

Describe the solution you'd like
A way to create or import a CALL HISTORY file.
When choosing the contest, not1mm automatically imports the contest's call history.
When filling in the CALLSIGN field, automatically, in the EXCH field, it is completed with the exchange of the station entered in the CALLSIGN field.

Describe alternatives you've considered

Additional context
RAEM.txt
@mbridak mbridak added the enhancement New feature or request label Jul 29, 2024
@mbridak mbridak self-assigned this Oct 30, 2024
@mbridak
Copy link
Owner

mbridak commented Oct 30, 2024

Okay this is the next Fun thing.

@py4xx
Copy link
Author

py4xx commented Oct 30, 2024 via email

@mbridak mbridak linked a pull request Nov 3, 2024 that will close this issue
121 call history #209
Merged
@mbridak mbridak reopened this Nov 3, 2024
@mbridak
Copy link
Owner

mbridak commented Nov 3, 2024

Hello @py4xx, I'm pretty far along in making this work.

So far I'm making it work with N1MM style call history files I've downloaded from their site that start with a header line defining how the info maps to the database table. For example you'd have to add:

!!Order!!, Call, Exch1,

Added as the first line of the RAEM.txt file you referenced in the your initial message.

I'll need to make a RAEM contest plugin, That's kind of a strange contest. Certainly has an odd point/multiplier system.

@mbridak
Copy link
Owner

mbridak commented Nov 3, 2024

Okay, I couldn't sleep. So I added a RAEM contest plugin. Got the Call History, ESM, crazy Points and Mult system working with it.

image

You'll have to be the bug hunter for this.

To Start:

Modify your RAEM call history file and add this header:

image

Then go to File -> Load Call History File Select your modified RAEM.txt file.

Then File -> New Contest, choose RAEM. For the exchange just put in your latlon.

image

Then File -> Configuration Settings, select the Options TAB. and enable the ESM and Use Call History checkboxes.

image

Then give is a spin and let me know if I got close.

@mbridak
Copy link
Owner

mbridak commented Nov 3, 2024

Oh yeah, your exchange macro should be # {EXCH}.

@mbridak mbridak closed this as completed Nov 8, 2024
@py4xx
Copy link
Author

py4xx commented Nov 8, 2024 via email

@py4xx
Copy link
Author

py4xx commented Nov 8, 2024 via email

@mbridak
Copy link
Owner

mbridak commented Nov 8, 2024

I wrote it to support n1mm call history files. The RAEM one can be found at:

https://n1mmwp.hamdocs.com/mmfiles/raem_2024-txt/

@py4xx
Copy link
Author

py4xx commented Nov 9, 2024 via email

@mbridak
Copy link
Owner

mbridak commented Nov 9, 2024

You should use the ESC key to clear all fields.
This will clear the both the call and any exchange.

Re: FLDIGI Hmm that's a new one. I'll look at it.

@mbridak
Copy link
Owner

mbridak commented Nov 9, 2024 •
edited
Loading

Re: FLDigi
Screenshot From 2024-11-09 15-14-34

Mine live happily together...

Maybe launch not1mm from a terminal window and see if it spits out a traceback when it quits.

@py4xx
Copy link
Author

py4xx commented Nov 10, 2024 via email

@mbridak
Copy link
Owner

mbridak commented Nov 10, 2024

Okay. I noted in your video that your using flrig. So I switched over to use flrig. Then fldigi locked up and became unusable. I wasn't able to change modes.

So I'm going to assume something is hosed with my flrig interface. This would make sense since I hate flrig and try to avoid it whenever possible. I'll put my big boy pants on to work with it more.

I'm going to open a new issue for this, since it's different from the initial problem/request.

@mbridak
Copy link
Owner

mbridak commented Nov 11, 2024

@py4xx Please see issue: flrig... I hate it. It hates me. #212

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mbridak mbridak

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

121 call history mbridak/not1mm
2 participants
@mbridak @py4xx