Decimal separator for region not adhered to

11 views
Skip to first unread message

Torbjörn Toreson

unread,
Oct 5, 2025, 5:24:34 AM (yesterday) Oct 5
to digitalvoice
Using Win11. In ver 2.0.1 the decimal separator for the frequencies in "Report Frequency. (kHz)" was shown according to the regional settings in the computer, eg comma for decimal separator in Sweden. In ver 2.0.2 this is not adhered to, instead the decimal separator is shown as a point. The latter will result in that the frequency setting of the transceiver will disregard the decimal, eg 5403.5 kHz will show as 5403.0 kHz on the transceiver. Please adjust.

73/SM6AYM

Torbjörn Toreson

unread,
Oct 5, 2025, 5:52:05 AM (yesterday) Oct 5
to digita...@googlegroups.com
A though: I may be easiest to make this a setting in Options, where you could choose point or comma as decimal separator. With point the default setting since most users have a point as decimal separator?
73/SM6AYM

5 okt. 2025 kl. 11:24 skrev Torbjörn Toreson <torbjorn...@gmail.com>:

Using Win11. In ver 2.0.1 the decimal separator for the frequencies in "Report Frequency. (kHz)" was shown according to the regional settings in the computer, eg comma for decimal separator in Sweden. In ver 2.0.2 this is not adhered to, instead the decimal separator is shown as a point. The latter will result in that the frequency setting of the transceiver will disregard the decimal, eg 5403.5 kHz will show as 5403.0 kHz on the transceiver. Please adjust.

73/SM6AYM

--
You received this message because you are subscribed to the Google Groups "digitalvoice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/e8e82f3a-8818-41f0-b2c6-d3157d435314n%40googlegroups.com.

Mooneer Salem

unread,
Oct 5, 2025, 7:13:57 PM (23 hours ago) Oct 5
to digita...@googlegroups.com
Thanks for the report. This is a known issue and has been added to GitHub for tracking as https://github.com/drowe67/freedv-gui/issues/1049.

-Mooneer K6AQ

Torbjörn Toreson

unread,
11:42 AM (6 hours ago) 11:42 AM
to digita...@googlegroups.com
Thanks for the reply Mooneer. I studied #1049 and that is a different case from what I reported. #1049 deals with what is reported to FreeDV Reporter. My case is the controlling of the radios frequency setting via Hamlib.

As mentioned, when selecting eg a frequency such as 5403.5 the radio will be set to 5403.0, disregarding the 0.5 kHz, and that is because my computer has comma as decimal separator and not a point. If I change the point to a comma in ”Report Frequency (kHz)” the radio will go to the expected 5403.5 on its display. In version 2.0.1 the decimal separator was according to the Regional setting in the computer.

By the way: The label ”Report Frequency (kHz)” seems to me to be somewhat misleading. I think most people use the dropdown list to select a frequency setting for their radio. Albeit the same setting will be used for reporting to FreeDV Reporter if that is selected in Options. My suggestion is to simply change the label to ”Frequency kHz”.

73/Torbjörn/SM6AYM


Mooneer Salem

unread,
3:58 PM (2 hours ago) 3:58 PM
to digita...@googlegroups.com
Hi Torbjörn,

I did some more testing before your reply and realized that CAT control was affected too, so I updated the GitHub issue accordingly. Fortunately, I do have a fix in testing now so that should get into master soon. 

Re: Report Frequency, I'll think about this some more. It might be a good idea to have this available for CAT control purposes even if a user chooses to disable reporting.

Thanks,

-Mooneer K6AQ

Reply all
Reply to author
Forward
0 new messages