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@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] DX4Win wish list (In addition to xmmt.ocx)
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 vk...@wallsy.com.au Mobile 0418 301 483 -Original Message- From: dx4win-boun...@mailman.qth.net [mailto:dx4win-boun...@mailman.qth.net] On Behalf Of K0CF Sent: Saturday, 12 October 2013 5:06 PM To: dx4win@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@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] DX4Win wish list (In addition to xmmt.ocx)
Maybe I am silly because I reply to the same question a number of years without response... Anyway... I like to add to K0CF list, omnirig support. This adds flexibility and solves a number of problems as 1. support for new radios (dx4win is also back on this), 2. co-operation with pst rotator (multiple rotors)... and maybe others... 73 Kostas SV1DPI __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] DX4Win wish list (In addition to xmmt.ocx)
I am on the air since 1991. I am using dx4win since december 1997 (release 1.07 if i remember well). I think that this software is just perfect. My wish list is limited to an improvement of CAT. I know that is a very hard job but in my opinion is the only part that can be discussed. I saw easy log. It gives a number of radio and a small customizable panel with the preferred controls for each one. I really don't need an HRD cat system but something more than what it is given today. That's all. 73 de Tibor IK2SAI Tibor M. Blum - IK2SAI - Inviato da iPhone Il giorno 12/ott/2013, alle ore 08:06, K0CF k...@mchsi.com ha scritto: 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@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
[Dx4win] DX4Win wish list (In addition to xmmt.ocx)
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@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] DX4Win wish list (In addition to xmmt.ocx)
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@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] DX4Win wish list (In addition to xmmt.ocx)
I'd like to say how much I truly enjoy using DX4WIN with all its capabilities and flexibility. Having AD1C doing the tremendous job of keeping so many things up-to-date and working properly is fabulous! Here is something I'd like to see. When I work a station that hasn't been spotted, I'd like it to appear on the BandMap without me needing to spot it myself. And, I'd like to be able to enter a station on the BandMap without working it or spotting it just like can be done with CTRL+ENTER on many Contest Programs. Either of these would allow me cruise the Band and know who is where without clogging up the Packet Network with some spots that no one else might care about. TNX/73, Bob K8BL From: K0CF k...@mchsi.com To: DX4WIN@mailman.qth.net Sent: Friday, October 11, 2013 12:28 PM Subject: [Dx4win] DX4Win wish list (In addition to xmmt.ocx) 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@mailman.qth.net This list hosted by: http://www.qsl.net/ Please help support this email list: http://www.qsl.net/donate.html __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Dx4win] DX4Win wish list (In addition to xmmt.ocx)
Hi! My two cents: -What about the automatic reconnection of DX cluster if it lost connection? WinTest can do it - More then one antenna rotor support - many HAM's have two or even more towers/rotors - When DX4WIN is started, the last QSO in the log is displayed and you should always push F9 to start logging - why? 73! Mike R3BM -Original Message- From: dx4win-boun...@mailman.qth.net [mailto:dx4win-boun...@mailman.qth.net] On Behalf Of K0CF Sent: Friday, October 11, 2013 8:29 PM To: DX4WIN@mailman.qth.net Subject: [Dx4win] DX4Win wish list (In addition to xmmt.ocx) 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@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
