www.dl2rum.de

Hi there,

the ADIF format supports the field MY_GRIDSQUARE. Wouldn't it be possible that Rumlog uses this locator (if given) to compute the distance for a QSO and not always just the generic one entered in the preferences? I think several people operate from different location sometimes and this would be rather nice.

73,
VK2UTL

It's a good point, but hard to implement.
The MY_GRIDSQUARE field is in the logging mask only and valid for the current QSO only.

Is that really that complicated? (Sorry for the direct question, I obviously don't know the internals). There must be some kind of an OnClick handler for a QSO row and at some point in there you compute the distance using the generic locator. Can't you just extend this piece of code by an if branch where you test if MY_GRIDSQUARE is set for the QSO and if yes then use this for the distance computation? I mean essentially all functionality must already be implemented.

Well, this may be easy, but this will work in the main logging window only. There are a lot of other places where the grid square is used. The Preferences is the central point where all parts of the application have access. An example: The DX-Spot window don't know, what you have entered in the logging window.

How about an option to take over the grid square from the Preferences to the MY_GRIDSQUARE field ? Then you have to enter your grid square only once after a QTH change.

Keeping track of my QTHs is not a real issue. It's just that I would like to browse around and find my most distant QSO on a given band or in a time window etc. So, it's primarily really about the distance display in the middle of the main window (see image). If there could be an additional field with the distance and heading relative to MY_GRIDSQUARE if given that would be absolutely perfect. Perhaps you can find a nice way to add such statistics.