WriteLog
[Top] [All Lists]

Re: [WriteLog] Feature requests

To: <writelog@contesting.com>
Subject: Re: [WriteLog] Feature requests
From: "Don Hill AA5AU" <aa5au@bellsouth.net>
Date: Tue, 15 Jul 2014 21:46:12 -0500
List-post: <writelog@contesting.com">mailto:writelog@contesting.com>
#5 - You can click on the first letter of a callsign that is not highlighted 
and it should populate the Entry Window.

Here is a nifty utility program caked Fkeys written by Keith, K7KAR, that works 
with WriteLog where you can use the mouse to send
RTTY messages. I don't use Fkeys although I probably should, at least to check 
it out.

http://www.kregli.com/fkeys.htm

You can program the buttons in the Entry Window to send messages too. See 

http://www.rttycontesting.com/writelog/rttystarter/starter_page10.htm

#6 sounds interesting, however it would require the user to run AFSK. Not so 
sure it would work in a crowded band during a contest
but would be interesting to see how it works.

#7 I'm a little confused on this one. You can program the F-keys any way you 
want and for any mode. Perhaps you might be referring
to multi-mode contests where you need a set of messages for each mode during 
the same contest?

"I know there are other programs that can run RTTY much better that Writelog 
currently does..." I have to disagree with you on this
one. If there were a better program for RTTY contesting, I would be using it.

73, Don AA5AU

-----Original Message-----
From: WriteLog [mailto:writelog-bounces@contesting.com] On Behalf Of Darren 
Collins (G0TSM)
Sent: Tuesday, July 15, 2014 4:51 PM
To: writelog@contesting.com
Subject: [WriteLog] Feature requests

Writelog is still my preferred contest and DXped logger. Some things I would 
like to see improved/added are:

1) Triggering of the FTDX5K's onboard DVK by the 'F' Keys. I thought there was 
a workaround for this but cannot find it.

2) SO2V support for the FTDX5K. Like running 2 radios but the bottom call entry 
field is for the 2nd-VFO.

3) Could the check call function be expanded to warn me if I have one letter 
wrong in a suffix - a little tricky this one! But very
handy for running a weak pileup where you only get 3/4 of the call.

4) Better support for the IOTA contest. If I type in a DL call I would prefer 
to see a list of DL islands and if I enter the wrong
IOTA reference I want an error message.

5) For RTTY I prefer to use the mouse to click on a decoded highlighted call 
and then click on buttons to send the messages. I don't
think I can do this at the moment using MMTTY/MMVARI. I have to click on a call 
and click on the call entry window to be able to use
the F keys. (although calls do not always highlight so I have to manually type 
some of them into the call entry window). Also you
can't right-click on a string and grab that as a call.

6) Support for 24 channel MMVARI in RTTY. Open up the Rx filter, run the pileup 
up split and let MMVARI decode the pileup, its
amazing to see and can give you an excellent DXPed run rate on RTTY.

7) Allow separate messages for RTTY in the CW/RTTY/SSB Memories. Yes you can if 
you use the shift button but try pressing that down
for a few hours at a time. When I was going back to CW I was pressing the wrong 
keys...

  I know there are other programs that can run RTTY much better that Writelog 
currently does but I do not want to have to keep
swapping programs, exporting the ADIFs etc.. Its a pain when you can be making 
QSOs.

Well, if you don't ask, you'll never get...

73 Darren G0TSM





_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4716 / Virus Database: 3986/7860 - Release Date: 07/15/14

_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/

<Prev in Thread] Current Thread [Next in Thread>