Hi Roger,
On the function keys not sending, what I have found is that usually your
cursor is not in the entry window of the program. It's actually easy to not
have it there since - depending upon where you put your windows and whether
they are docked or not - you can move around with the mouse real nice. So,
first, insure your cursor is in the log entry window.
Second, if it is in the log entry window, pressing Escape clears the
'whatever' to allow you to send the function key. I haven't had this problem
since I have done these two steps.
On the highlighting of the calls being one letter short - this happens quite
frequently. Partly because the call highlighted is also one in the database,
partly because of the logic, etc., etc. The thing that drove me crazy this
weekend was that I would click on the call in the RTTY window to get it in
the Entry Window, then manually correct the call to get it right, then hit
Insert key (CT Compatibility here for function keys...) to send the correct
call, and it would revert back to the old incorrect call. No fun, drove me
crazy.
After playing with it a bit, it turns out that this is a feature (one
person's feature is another person's nemesis...). If the call is correctly
highlighted, all you have to do is hit the Insert key and the program
AUTOMATICALLY takes the last highlighted call from the RTTY window, puts it
into the Entry window, pulls the correct zone (or exchange) information,
puts your cursor up in the Entry window, and sends the report. Pretty slick.
What if the call is not fully highlighted? Get the call into the entry
window (manually type or click on the highlighted part to move it to the
entry window and then edit the call to make it correct) and then hit F10.
NOT the Insert Key. F10 will send what is in the entry window as it stands.
Now, of course, being tired, I sometimes screwed this up, but the idea is
less work if correct and hitting the Insert key, and F10 to send corrected
calls in the entry window.
Making all this easy is hard work...
CU...Scot, K9JY
mailto:scot@k9jy.com
www.k9jy.com
I'm still new to Writelog, 2nd contest. First RTTY contest with Writelog.
Program worked great except for two small problems. On occasion, when I hit
F2 to sent my response, the program would send the F4 information or
sometimes do nothing. This happened about 1-2 dozen times. I have no idea
why, dumb ME or the program?? Anyone else have this problem or know why it
happens. Also an even more minor problem, sometimes when a call in the RTTY
window was highlighted the highlighting was off by one space.
I'm running with Windows Me, Writelog, and DX4WIN. I think I have all
Windows programs now. It's really nice. I don't think I'll ever use CT
again.
73, Roger, W1EM
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|