Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Callsign lookup
|
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 log, the information is also transferred to DXView which then provides beam heading and progress information. However, if the callsign does not exist in the log, nothing goes to DXView. I could click "lookup" to get the call into DXView but that does other things including noting the start time and I haven't started a QSO yet. ----- 73, Rich - W3ZJ www.w3zj.com |
|
Dave, AA6YQ
We can certainly change "?" from "check for previous QSOs" to "check for
toggle quoted message
Show quoted text
previous QSOs and lookup DXInfo but don't set the start time". Seems a little complicated to remember. Or we could modify the "lookup" button to not set the start time, perhaps making start time the same as end time for all QSOs logged throught the capture window. Or should I add a "start QSO" button to record the start time? Which would be more intuitive and/or convenient? Is there a better idea? 73, Dave, AA6YQ -----Original Message-----
From: Richard B Drake [mailto:rich@...] Sent: Tuesday, April 03, 2001 23:40 PM To: Dxlab Subject: [dxlab] Callsign lookup 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 log, the information is also transferred to DXView which then provides beam heading and progress information. However, if the callsign does not exist in the log, nothing goes to DXView. I could click "lookup" to get the call into DXView but that does other things including noting the start time and I haven't started a QSO yet. ----- 73, Rich - W3ZJ www.w3zj.com Yahoo! Groups Sponsor To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. |
|
Ron Eberson
A button so that we can make a choce in it than we can use it also for
contests. my opinion Ron -----Oorspronkelijk bericht----- Van: Dave, AA6YQ [mailto:dhb@...] Verzonden: woensdag 4 april 2001 7:39 Aan: dxlab@... Onderwerp: RE: [dxlab] Callsign lookup We can certainly change "?" from "check for previous QSOs" to "check for previous QSOs and lookup DXInfo but don't set the start time". Seems a little complicated to remember. Or we could modify the "lookup" button to not set the start time, perhaps making start time the same as end time for all QSOs logged throught the capture window. Or should I add a "start QSO" button to record the start time? Which would be more intuitive and/or convenient? Is there a better idea? 73, Dave, AA6YQ -----Original Message----- From: Richard B Drake [mailto:rich@...] Sent: Tuesday, April 03, 2001 23:40 PM To: Dxlab Subject: [dxlab] Callsign lookup 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 log, the information is also transferred to DXView which then provides beam heading and progress information. However, if the callsign does not exist in the log, nothing goes to DXView. I could click "lookup" to get the call into DXView but that does other things including noting the start time and I haven't started a QSO yet. ----- 73, Rich - W3ZJ www.w3zj.com Yahoo! Groups Sponsor To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to |
|
Dave,
toggle quoted message
Show quoted text
As you probably know, some countries (the UK for example) still require logging of both start and stop times. Here, we can do what we want including nothing. But, QSLing dictates that we record times as accurately as we can so that we can reasonably confirm a contact. Thus, this is the reason for even being very concerned about it. Most loggers record only one time and there has been a big discussion lately on the OnLineQSL reflector as to whether to record the start or the stop time. Interestingly, it splits about 50/50 among users and people have reasons that they consider important for doing it one way or the other. DXKeeper is one of the few loggers that records both the start and stop times so this becomes an important feature of the program. I think your idea of providing a separate button specifically for noting start time is the best. No one will be confused about it and it provides complete control over it. My suggestion would be that it not be a required entry and if the user doesn't select it you record the time of entry into the log (basically the end time of the QSO) in both time fields. This will work out well for those quick DX and contest contacts where start and stop times differ only by a few seconds and also provides rag chewers with a way to record both times on a long QSO when they want it. ---- 73, Rich - W3ZJ -----Original Message----- |
to navigate to use esc to dismiss