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

Improve Frequency input #165

Open
205er opened this issue Feb 22, 2024 · 6 comments · May be fixed by #285
Open

Improve Frequency input #165

205er opened this issue Feb 22, 2024 · 6 comments · May be fixed by #285
Labels
enhancement New feature or request frontend things which are affecting Frontend/UI

Comments

@205er
Copy link

205er commented Feb 22, 2024 •
edited

Hi all,

When displaying a QSO, the frequency will be shown in the following way: 21.300 - Frequency in MHz with dot as decimal separator and three digits as decimal. Unfortunately, you cannot enter a frequency in this format, but it must be entered in Herz. To stick to my example: 21300000 must be entered! If you enter 21.300, the frequency will not be overtaken correctly, but set to the value 21 and displayed as 0.000

Would it be possible to improve this behavior or at least implement a check, so that the input does not get lost?

Freq
Freq

73
@HB9HIL HB9HIL added frontend things which are affecting Frontend/UI enhancement New feature or request labels Feb 22, 2024
@HB9HIL
Copy link
Contributor

HB9HIL commented Feb 22, 2024

Hello @205er

this is a fair point. We may add a User Option for it so the user can decide which format he wants to use 👍

@205er
Copy link
Author

205er commented Feb 22, 2024

Thanks for your quick and positive response.
At least, it would be greate to have the input checked (ideally directly when leaving this field and not only when the QSO will be saved). This would help to prevent input mistakes.
Making the input user defined would be wonderful! So to say the cherry on the cake 😄

@dg9vh
Copy link

dg9vh commented Feb 29, 2024

Good idea... it could be checked against the band-value (if selected) or against some bandplans that in ideal world could be customized by the users with it's boundaries.

@dg9vh
Copy link

dg9vh commented Feb 29, 2024

We may not need to have them customizable... was a wrong bias in brain :-)

@205er
Copy link
Author

205er commented Mar 13, 2024

Today i tried out SFLE, which is an fantastic feature! Frequency input in MHz with decimal separator "." is possible (e.g. 21.304) there.
The standard QSO input will not accept this freq. format. :-( Additionally, the band indicator is not logically linked to the frequency, which means you could enter "21,304 MHz" but the band is still set to "80m". When having some pileup, this would easily lead to inconsistency in the heat of the moment.

@HB9HIL HB9HIL linked a pull request Apr 15, 2024 that will close this issue
Draft
@HB9HIL HB9HIL linked a pull request Apr 30, 2024 that will close this issue
Frequency Unit #285
Draft
@HB9HIL
Copy link
Contributor

HB9HIL commented May 3, 2024

This will take a bit longer since it's quite complex in the qso logging and I need time to dig into this. Please have some patience

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request frontend things which are affecting Frontend/UI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Frequency Unit HB9HIL/wavelog
3 participants
@dg9vh @205er @HB9HIL