[Dx4win] 6.03 usage report, suggestions for enhancement

[L. Sica]

Let me clarify.... a seperate window for *entering search criteria to browse
the log", and another seperate window to *add an entry to the log*. That way
you can have QSO details for your current QSO in one window, and a search
criteria for your existing log entries in another, so you don't loose the
QSO data you're entering if you want to search your logbook.

----- Original Message ----- 
From: "J. F. Samuels" <k2cib at arrl.net>
To: "L. Sica" <lsica at comcast.net>; "DX4WIN List Server"
<DX4WIN at MAILMAN.QTH.NET>
Sent: Saturday, July 10, 2004 11:55 PM
Subject: Re: [Dx4win] 6.03 usage report, suggestions for enhancement


> Gee, Lou, you must have missed number 4.  Try Window | Logbook.  And,
right
> click and see the options.
>
> John, K2CIB
> ----- Original Message ----- 
> From: "L. Sica" <lsica at comcast.net>
> To: <support at dx4win.com>; "dx4win reflector" <dx4win at mailman.qth.net>
> Sent: Saturday, July 10, 2004 9:49 PM
> Subject: [Dx4win] 6.03 usage report, suggestions for enhancement
>
>
> > This message is being sent to the DX4Win reflector and to DX4Win support
> >
> > Having used 6.0.3 for a bit now, I feel I can make some comments on it.
By
> > far for the most part, it's a good update. Most of what I use of the new
> > features is the LOTW interfacing features. A little confusing (as has
been
> > discussed on this reflector), but once you understand how to do it, not
> bad
> > at all. The DXCC submission now allowing for DXCC challenge submissions
is
> a
> > plus, too.
> >
> > DX4Win is the best DX logging program out there. Other programs are slow
> > (even making my Athlon XP 3000 box seem like it's struggling a bit), or
> are
> > SO FULL of things to adjust (I don't want to have to spend an hour
> adjusting
> > every font and every color on every window) or so full of "features"
> > (digital voice keyers, beacon tracking, etc) that they skimp on basic
> stuff
> > like DXCC awards submission or any sort of WAZ tracking at all. DX4Win
is
> > fast, it has easy to read windows, and it covers the needs of a logging
> > program (data entry and reporting) very, very well.
> >
> > After saying all that, my suggestions
> >
> > 1) A better list of rotator directions for prefixes:
> > For example. every time I enter a UA0 or UA9 call, DX4Win wants to
rotate
> my
> > beam to 353 degrees. Problem is, a ham in Asiatic Russia might be at a
> > heading of anywhere from 325 to 25 degrees from here. A more detailed
> prefix
> > list (UA9A, UA9K, UA0Z, UA0Y, etc, etc) would provide a better bearing
for
> > automatic rotator adjustment.
> >
> > 2) A date range and band filter  on the "Change Award Flags" selection:
> > DXCC cards submitted to "Field Checkers" can't include 160m cards or
cards
> > more than 10 years old. Being able to select these cards right from
DX4Win
> > would be a big help.
> >
> > 3) The ability to IMPORT from a CSV file:
> > Sometimes, you just want to make changes to multiple items in your log
> that
> > you know you just couldn't expect a logging program designer to think
of.
> > DX4Win can already export all fields to CSV. If it could RE-IMPORT those
> > fields after you did whatever magic you had to in your favorite
> spreadsheet
> > program, that would be sweet.
> >
> > 4) A seperate window for "browsing the log" than from "entering data"
> > This is something I used to have in a previous program some years back,
> and
> > I have gotten used to not having it. Still I miss not having to lose the
> > current entry in my log window just because I want to do a search
through
> my
> > log to see what QSO's meet a certain critera.
> >
> > Thanks to all (including Paul) for listening to my suggestions.
> >
> > 73 de Lou AC0X
> >
> >
> > _______________________________________________
> > Dx4win mailing list
> > Dx4win at mailman.qth.net
> > http://mailman.qth.net/mailman/listinfo/dx4win
> >
>
>