Version 2.20
Selected "Distance" to display on Recent QSO table and noticed the distances are all in km even though my program distance setting is for miles.
73 de Larry
N1FG
QSO Distance always in km - regardless of config setting
QSO Distance always in km - regardless of config setting
- Attachments
-
- Log4OM Settings.JPG (89.88 KiB) Viewed 1653 times
-
- Log4OM Recent QSO.JPG (216.88 KiB) Viewed 1653 times
Re: QSO Distance always in km - regardless of config setting
I’ve noticed the same, using 2.21.1.0 here. Distance is always displayed in km, even though set to miles.
73, M7WWX
73, M7WWX
73, Simon, M7WWX
- G4POP
- Log4OM Alpha Team
- Posts: 10803
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: QSO Distance always in km - regardless of config setting
Because ADIF standard records distance in km
73 Terry G4POP
Re: QSO Distance always in km - regardless of config setting
So what’s the point of the distance setting? Can’t the app convert km into miles?
Regards,
Simon
Regards,
Simon
73, Simon, M7WWX
- G4POP
- Log4OM Alpha Team
- Posts: 10803
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: QSO Distance always in km - regardless of config setting
1 For the display below
2. We could but dont
2. We could but dont
73 Terry G4POP
Re: QSO Distance always in km - regardless of config setting
I mean in the QSOs tab at the bottom. Why can’t those distances be converted into miles?
73, Simon, M7WWX
Re: QSO Distance always in km - regardless of config setting
So... you use that configuration selection for one calculation on one screen? (If that's as much good as it does why not make it a button selection on the map screen itself, or why use miles there at all?)
Speaking for my operating routine I very rarely even look at the "main" screen as I am usually either on Recent QSOs or Worked before.
However, thanks for the explanation.
73 de Larry N1FG
Speaking for my operating routine I very rarely even look at the "main" screen as I am usually either on Recent QSOs or Worked before.
However, thanks for the explanation.
73 de Larry N1FG