开云体育

I just worked BX7AA on 21.016. I ran the propagation forecast for him using the current solar flux of 228 (not too shabby) and it showed that I should have propagation but it was between the 10% and

To get full interoperability between DXView and PropView, you should be running DXView 1.2.6 -- sorry for not making this explicit. 73, Dave, AA6YQ

Ron, are you still having problems with PropView settings like Power and TakeOff not being saved between sessions? Is anyone else encountering this? 73, Dave, AA6YQ antenna? see the

No dave with the last update all are great no problem. sorry to tell you not before. -----Oorspronkelijk bericht----- Verzonden: donderdag 5 april 2001 17:18 Aan: dxlab@... Onderwerp:

I have resized DXKeeper already as you had described but I was running 600 x800 resolution. I have up 1024 x 768 It is a little better. The font is smaller but I fortunately have my eyesight. My

I use it that way also Dave. I assume you meant that you type the callsign into the capture window and hit enter. I would still like to see it do one more thing when you hit enter on a callsign in the

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

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

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

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"

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

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

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 -

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

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

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

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

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

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

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