开云体育

The "lookup last log entry" blemish is fixed, and clicking Lookup (in the Capture window) now restores input focus to the Callsign textbox. If nothing else shows up for a few hours, I'll release these

You can install the latest update. Dave

Dave, I have used V121 this afternoon to log several contacts and it seems to be working well now. One thing that seems strange is that after logging a contact it picks up the callsign of the

Hi Dave, Is it necessary to install each update individually or does the latest one encompass all updates befor it. I am not able to install each update as they become available. Instead, I have to

It wouldn't be a problem to have it all in one application. Personally I have no access to a VHF packet cluster so the most I would use would be two or three Netclusters and maybe an IRC cluster (I've

Thanks for your participation, Tom! Dave, AA6YQ

I hope that SpotCollector is next on your to do list. I find that absence of that is the major reason that I keep reverting to Logger. I think that once the bugs are worked out and

Hi Dave, I have upgrade DXView to 1.2.3 and DXKeeper 1.1.7 and will install the latest updates as soon as my work schedule calms down. Having the capture window is exactly what I was looking for. I

Hmm! I thought I tried that and it didn't work, but I just tried it again and it does work. I'll bet I clicked on "Go" in stead of pressing enter. I hope that SpotCollector is next on your to do

You can enter lat/lon directly; enter an angle (e.g. 24 12'N ) and then strike the Enter key. Hiding the map is certainly feasible; I'd have to find room for a button that toggles between ShowMap and

Dave, I use most of the fields as they are with the exception of region and time. I would like to see the ability to enter Lat/Lon and calculate the heading. I monitor the Maritime Mobile Service

That's basically it. At one point I thought I saw it clobber an existing log entry by changing the time/date and band but when I tried to reproduce that, I couldn't. Perhaps it was caused by

The title bar UTC clock does not function in this release -- I disabled it while debugging something, forgot to restore it, and failed to notice its condition during pre-release testing. I'll

In the release - there is no longer a "current time" setting - when the Prediction tab's "Show Current Time" box is checked, the Vertical Time Index automatically tracks the current time -

I noted two QSO Capture window defects in the scenario outlined below: #19: clicking the Log button failed to unfilter the log #20: the recorded QSO start time is bogus Was there something

Dave, Try the following. In the capture window, enter a callsign of a station that "is" in your log, press enter. All looks fine so far, does the lookup - great. Now click log to log it. Whacky!! If

This release adds a "Display Previous QSOs on Lookup" checkbox to the "QSO Capture window" panel of the General configuration tab. When this box is checked, clicking the QSO Capture window's "Lookup"

Magic, Dave! I just upgraded my version of dxview to 1.2.6, and now it works perfectly with PropView. Thanks! Robin gw3zcf should

Yes, if it's easy to make it configurable, why not? Like you, I have a large screen monitor (21") and run it at 1280 X 1024 resolution so screen real-estate is less of a problem for me than it is for

I like the simplifying aspect of this proposal -- it eliminates the ? button to the left of the callsign. The Lookup button would do everything. But it does mean that every "Lookup" will result in