Helo all. I have install the 1.01 version of PropView. I have the next problem. 1. When i click the Predict button the next mesagge show: Error 13 Run time error. 2. If i click the help button i have

This release corrects the runtime error occuring on systems with a locale that doesn't use the period character as a decimal separator. (Ron, this should correct the problem you are encountering with

Dave, Entering a callsign in DXKeeper's capture window and clicking on the question mark next to it causes the callsign to be placed into the filter window and looked up. If the callsign exists in the

Dave, Now that the solar flare activity seems to have settled a bit, PathView is providing some very nice and accurate information. I think however that it is not always reading the clock. When I firs

When PropView starts, it initializes the Time field to the then current UTC time. This won't change unless you change it -- either by double-clicking (to set the current time), or by keying in a time.

This release - adds an "Import from MMTTY" checkbox to the Import tab, which when checked extracts transmit and receive sequence numbers from imported RST sent and rcvd fields respectively - adds a "S

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 5

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 http://docs.yahoo.com/info/terms/

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 thoug

Hi Dave, Have just started using PropView and it seems to work well at this QTH. What would make it very quick to use would be the ability to use Country prefixes instead of Latitude and Longitude. Al

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 y

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 - you can dra

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 else? Both

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 correct

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 do

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 previous

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 pi

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 SpotCollector imple

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