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

[Ernie Walls]

I have only ever wanted one thing 'fixed' - the ability of the DX4Win logging program to retain the correct name/address information per QSO, regardless if the call sign has been logged before, or not.

That a logging program cannot do that simple thing (remember, logging programs are/should be simple data collectors [or databases, to put it more correctly]) has always frustrated me - because I must use a 'workaround' to retain correct data (important data) rather than have the program do it property in the first place.

And, I am well aware it will never be fixed (too hard, I was once told) but - that's my wish.

Oh well....!

Ernie Walls VK3FM
vk3fm at wallsy.com.au
Mobile 0418 301 483

-----Original Message-----
From: dx4win-bounces at mailman.qth.net [mailto:dx4win-bounces at mailman.qth.net] On Behalf Of K0CF
Sent: Saturday, 12 October 2013 5:06 PM
To: dx4win at mailman.qth.net
Subject: Re: [Dx4win] DX4Win wish list (In addition to xmmt.ocx)

With my previous post, I was hoping to produce a discussion of improvements needed in DX4Win, and we have a reasonable start. Some comments for a couple of the replies:

To Joe, W4TV, I respectfully disagree. In 54 plus years of hamming I have found things that work for me. My suggestion of how I like to log receive, transceive and transmit frequencies has evolved over time, primarily in the age before computer logging, when I wrote QSL cards out by hand and used frequency rather than band.
The DX station needs to see his transmit frequency on my QSL, not mine, which he doesn't log anyway.
By doing receive/transceive frequency in one column and my transmit frequency in a separate column, I could always use the first frequency column in filling out the card, regardless of whether the QSO was simplex or split. I still prefer that arrangement for browsing my logs -- I want to see the DX's frequency first.

I very well know the definition of QSX, but it doesn't really have anything to do with how I like to log QSO info. And it must be noted that my transmit frequency is ALWAYS logged by this method.

And to Mike, R3BM, thank you for jogging my memory! I just had this nagging feeling that there was something I was leaving out, and auto connection to the cluster is it. Not just reconnect after interruption, but automatically connecting on DX4Win startup. I always use the same node (unless it's down for some reason), so DX4Win should at least to try to connect on program startup. It is a real annoyance to have to go through the connect sequence every time I start an operating session (even though it is just a mouse click, three presses of "Enter"
and a mouse click on my "Login" macro button).
My login macro issues an SH/DX/100 command to immediately populate the Spots window, and it would be nice if DX4Win did that as well. Both DXLab and HRDeluxe automatically connect on startup.

Support for two rotators would be nice for those who are lucky enough to have two or more towers. I have only one 40 foot tower, so that feature wasn't on my list.

Well, guys... What do you think needs to be added or fixed for the next release?

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