开云体育

I understand Rich's suggestion to be "striking CTRL-Enter in any QSO Capture Window textbox logs the current information and clears all fields for the next QSO". Should the same behavior apply in

You meen a special button for this Richard that likes great not mistakes to the put two buttons good idea. Ron -----Oorspronkelijk bericht----- Verzonden: vrijdag 20 april 2001 17:49 Aan:

Dave, So far the new versions of DXKeeper and DXView are running smoothly but we'll run them a little longer before giving a clean bill of health :-) I like the new functionality. One thing, I would

That's certainly a defect, Mark, but you're the first to report it. What version of DXView are you running? On which operating system are you running? Does this failure occur right away, or after you

I am having a problem getting "DxView to work. When I go to bring it up, I get a "Runtime Error 340 Control array Element '0' Doesn't Exist". Does anyone know what that means. Thanks in advance for

The correct URL for ARSWIN is http://www.ea4tx.com/inde.htm

This release - supports rotators controlled by ARSWIN (see http://www.ea4tx.com/inde.htm) - logs the contents of the Prefix texbox (presumably a callsign) in DXKeeper (if running) when you

This release - eliminates several possible causes of the "Cannot open any more tables or queries" error log entry that occurs after many log filter operations - accepts callsigns from DXView

This is a defect, Joe -- PropView's Transmitter Latitude and Longitude are not being properly initialized when DXView is installed. This has been corrected in PropView version 1.0.6, which can be

Dave, I have been running V 1.2.4 most of the day and so far I have been unable to break it. I created a new error log before installing it and so far it's empty. Looking good :-) ----- 73, Rich -

This release - correctly updates the progess table when QSOs are logged from the Capture window - contains more instrumentation aimed at isolating the "persistent hourglass" problem - if

Found something interesting about that. If you make a change to a contact in the main QSO window then click save, it adds the info to the progress window. Might help narrow it down a bit. ---- 73,

yes, I noticed that last night while hunting for the "hourglass" problem. I'll track it down... 73, Dave, AA6YQ

Dave, The progress table does not seem to get updated as I add new ones. I have to do a "Recompute" for them to show up. ----- 73, Rich - W3ZJ www.w3zj.com

That should be trivial to implement, once I find the Windows API for the mouse wheel. 73, Dave, AA6YQ

An interesting feature that was just added to WriteLog, is mouse wheel tuning of the radio - pretty slick. How about CI-V commander? I think 10Hz a click would be good, just right for a little fine

Actually very few programs offer the option to append. Most say overwrite, or name another file. Yes, it would be nice to say, it exists, overwrite it or append to it. I will almost always

So should DXKeeper note that the specified file exists and query the user with something like "The file c:\mylogs\mumble.adi" already exists -- should I clear its current contents before

Dave, I notice that when you export log entries to an existing ADIF file that you append the entries instead of overwriting the old file. Since I use this feature mostly to add new entries to eQSL.cc

Re "I think what we are trying to accomplish is to make the help files irrelevant if we possibly can." - that is precisely the objective. 73, Dave, AA6YQ