[DogParkList] MLDX Ideas for the future

[Rick Prather]

Lee,

Your wants for cluster and database functions are nearly the same as  
mine.

In my search for the functionality I want for my DXCC database I have  
looked in to several Windows logging programs (to quote you, YUCK)  
most of the OSX programs.

I managed to find the LoTW and "need" aspects of most of what you want  
in a program called RUMLog  by Tom DL2RUM.

Since I am now using both RUMLog and MLDX I would be a very happy dude  
if Don is going to incorporate the database features that RUMLog has  
in to the new MLDX.

The features I really enjoy are the "worked, confirmed" matrix that  
you mention but it also shows "worked, sent, exchanged status for not  
only paper QSL but also LoTW QSO's.   At a glance you can see the  
status for both methods of QSL'ing in the three modes on all bands.

Also, it has good LoTW integration in that you can generate a .tq8  
file from any contact that shows worked but not sent.  And, a feature  
I really like, you can have it check the ARRL server and download your  
confirmations and also change the status of the QSL automatically.  A  
real time saver.   I can also very easily generate reports of things  
like Countries confirmed on Paper only, on LoTW only or, my favorite,  
confirmed on LoTW only.

As far as the cluster is concerned it's Telnet program is amazing.  It  
will not only color code the countries you need or need confirmed but  
will also color code the mode and/ or band.  So, in a separate window  
from the general minutia window you will see only the countries you  
are interested in with the mode/band/ or country in general indicated  
by color code.  Very nice.

Having said all, as I mentioned I now have to run both programs to get  
the functionality I want.  MLDX is a much more complete and feature  
rich operating aid and also controls my rig.  Whereas RUMLog is where  
I look for spots and award needs.  Hence the rub, I constantly have to  
decide if I want the convenience of being able to double click a spot  
and have my radio go right to the Freq and mode or have the cluster  
sorting ability of RUMLog.

For now I will use both and let my mood decide how to watch the cluster.

Here's hoping that if Don hasn't already, he will take a look at Tom's  
logger and incorporate the best features of it in the new MLDX.

Rick
K6LE

On Apr 9, 2008, at 1:58 PM, Lee (WW2DX) wrote:


>

> Hi All, been using MLDX for a while now and I have put together a  

> list of observations thus far.

> Since I see see Don is working on a new cocoa version of MLDX ( yay)  

> perhaps this is a good time to

> place some feedback.

>

> This list is in no particular order. I just added them when I  

> thought or ran across them.

> Also I apologize up front if some of these features are already in  

> MLDX and I just did not find them.

>

>

>

> Long Path Azimuth reading

> 	- Currently short path azimuth reading is shown when a call or  

> prefix is looked up.

> 	Would be way cool to maybe click on the AZ box and have it switch  

> to the LP AZ and highlight in some other color

> 	so you know it's LP.

>

>

> AWARDS:

>

> Track WAS by Band.

>

> Display shows when a new grid is being worked (call lookup lets you  

> know its a new grid on that band)

> 	- I find that during a 6m opening I will do a call lookup of a  

> distant station. I then have to navigate

> 	to awards -> VUCC -> then look and see if the grid is needed.  

> Perhaps that when a lookup is done,

> 	and since the grid is shown in the lookup results, MLDX looks at  

> the freq and then compares with

> 	the current grid worked data. If it is not in that list the Grid  

> field changes color or some event happens

> 	to let you know instantly that it is a new one.

>

> Same for DXCC/WAS/ etc. I find that when I see a DX station come up  

> on the cluster I have to go to

> Awards the enter the band and then search down the list to see if I  

> have worked it and where I need it.

> It would be great if there was a field that in the main view where  

> it showed what bands where needed for that entry.

> Way back in the day when I used hyperlog it had a nice band map that  

> looked like something like this:

> 	

> 	- I would put his feature way up on my list of what I look for most.

>

> 	---------------------------------------

> 	- 160  80  40  30  20  15  10  6  -

> ssb	-   	   C			   W		  -

> cw	-   C		W           C                 -

> 	--------------------------------------

>

>

>

> WAC award tracking 5bwac

>

> WAS/WAC/DXCC by band 5BWAS/etc/etc/

>

> WAZ / Track each WAZ award.

> http://www.cq-amateur-radio.com/wazrules.html

> It would be nice for all of us paper chasers :)

>

> 	- I don't know how popular award chasing is today. Use to be a big  

> deal when I was a kid. As a paper chaser

> 	these are just things to keep me organized.

>

> DX Cluster:

> When a new or unconfirmed dxcc/state/vucc etc shows up mldx changes  

> the color of the spot to let you know either not conformed or not  

> worked

> depending on color. I don't know if this is possible, but I thought  

> it would be sweet that as dx spots popped up, MLDX would grep the  

> prefix and see if

> it is a new one. If so, some color for NEW and some other color for  

> NOT confirmed.

>

>

> Other Features:

>

> Support for Icom 275H/475H

>

> When switching modes that require a particular RST have MLDX  

> automatically change the RST appropriately.

> For instance, If you switch to CW change the RST field to 599/599,  

> if you switch back to U/LSB auto change RST to 59/59.

>

>

> QSL SNT/RX

> I like the green/red but a 3rd color may be helpful when you RX a  

> card but have not sent one yet.

> 	

>

> Electronic QSL services:

> The ability to automatically in real-time add QSO to eQSL and LOTW

> I believe eQSL does, not sure about LOTW.

>

> 	- Update, I think I have read someone here in the list that has a  

> applescript to do this.

>

> Recording live QSO and saving to log:

> I know there are apple scripts  but it would be cool to just click a  

> record button in MLDX to start a recorder in the backgound then log  

> the recording with the log entry.

> You could have a little play button in the log. Neat :)

>

>

> Multiple Rigs:

>

> Hot button on main page to switch to other rig.

> Also pre-set which rig gets which freq.

>

>

> Google Earth plotting. Have MLDX grep the LAT/LON from qrz and then  

> be able to plot your Q's in Google Earth. I do this a lot for my VHF/ 

> UHF contests.

> For example: I had to export my log to Ham Radio Deluxe and use the  

> export to google map function there (YUCK).

>

> http://www.ww2dx.com/Site/Blog/7539304B-36FA-4983-A9CE-659E0AD4C1A5.html

>

>

> Option to use Growl for DX cluster spots.

>

>

> Bug?

>

> Resizing the app after removing 23" cinema.

> 	- When I had one, there was a issue when I disconnected the cinema  

> display the MLDX window stayed the same size

> 		on the native 15" TFT. I had to close and reopen MLDX to resize.

>

>

>

> OK, so that is what I have so far. I have to say that I really enjoy  

> MLDX a lot. I also get countless compliments when I show the  

> software to other non mac hams. Kudos to Don for a great software  

> package and keeping with the true feel of what a MAC is and should be.

>

> Looking forward to the next release!

>

> I am open to any comments or thoughts anyone has about the above.

>

> 73 and CU in the pileups!

>

> de Lee

> WW2DX

> http://www.ww2dx.com

>

> MLDX/MBP/K3 - Does life get any better? :)

>

>

>

>

>

>

> _______________________________________________

> DogParkList mailing list

> DogParkList at dogparksoftware.com

> http://two.pairlist.net/mailman/listinfo/dogparklist


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://two.pairlist.net/pipermail/dogparklist/attachments/20080409/11feb2a0/attachment-0001.html>