[Dx4win] DX4Win wish list (In addition to xmmt.ocx)

[Joe Subich, W4TV]

 > Proper logging of split frequency operation.
 > The Frequency box should always be the receive
 > frequency, i.e. the frequency that the DX is
 > transmitting on. The QSX (transmit) frequency
 > should be logged in a field separate from the
 > current Frequency box only if operating split.
 > (It is currently done in reverse from this.)

Frequency recoding is *correct* now ... one should
*always* log the frequency *on which he transmits*.
The frequency on which one is receiving should be
logged as the "receive frequency" or QSX frequency.

As a point of fact, the definition of QSX as a statement
is: "I am *listening* for [call] on [frequency]"

73,

    ... Joe, W4TV


On 10/11/2013 12:28 PM, K0CF wrote:
> DX4Win is certainly due a "refresh". My wish
> list (in addition to xmmt.ocx support) for
> the next release includes the following:
>
> QRZ.com XML data subscription support in the
> F3 Callsign/Mgr Lookup window. This is LONG
> OVERDUE! Having to use a callbook CD is so
> archaic and annoying, since they are out of
> date as soon as you get them.
>
> Automatic removal of "old" spots from the DX
> Spots window (as happens in the BandMap). A
> Preferences option to control this behavior
> would be nice. That would keep those who
> like it the way it is happy, too.
>
> Smooth, clean and transparent disabling of
> the radio interface if the radio is turned
> off before shutting down DX4Win. Automatic
> re-establishment of the connection if the
> radio is turned back on. Other programs do
> this, e.g. WriteLog. An indicator on the QSO
> window that the rig interface is not working
> would be nice, e.g. a blinking red dot,
> showing "No Rig!" in the frequency box, or
> flashing frequency/mode info. But it should
> not hang DX4Win and demand that the operator
> click on a dialog box to proceed.
>
> Proper logging of split frequency operation.
> The Frequency box should always be the receive
> frequency, i.e. the frequency that the DX is
> transmitting on. The QSX (transmit) frequency
> should be logged in a field separate from the
> current Frequency box only if operating split.
> (It is currently done in reverse from this.)
>
> Well, that's my list of the biggest annoyances.
> I am sure there are others that I haven't
> thought of right now.
>
> I recently evaluated DXLab and HRDeluxe.
> Quite frankly, DX4Win is much better than
> either of these in ease of use, award
> tracking, award submission and many other
> areas. Not to mention AD1C's efforts on all
> the various database files! Now, if only it
> could be updated to fix the above problems,
> I would be a very happy camper!
>
> 73,
> Craig, K0CF
>
>
>
> ______________________________________________________________
> DX4WIN mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dx4win
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:DX4WIN at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>