As for the separate message memories, I usually start setting up a contest
by loading the messages from the last year's contest using the browse
function. You could also set up empty log files with default messages for
CW, RTTY, etc and just browse to them to change the messages. Just thought
of that, will have to try it myself.
On Wed, Jul 16, 2014 at 12:15 AM, Darren Collins (G0TSM) <daz@g0tsm.com>
wrote:
> No I didnt know about Fkeys so will look into that, although the
> screenshots on Keith's website appear to show what I would like.
>
> If I click on an 'un-highlighted' call it appears to end up in the
> 'Country' field when using the DXPedition module. I'll try this again later
> tonight on my main station.
>
> 73 Darren G0TSM
>
> On 16/07/2014 00:20, w4lc@fuse.net wrote:
>
>> Ref: your #5 Are you familiar with the Fkeys program by Keith Regli?
>> Also, decoded calls do not have to be highlighted to be clicked into the
>> entry window. Just click on the first character.
>>
>>
>>
>> ------------------------------------------------------------------------
>> *From: *"Darren Collins (G0TSM)" <daz@g0tsm.com>
>> *To: *writelog@contesting.com
>> *Sent: *Tuesday, July 15, 2014 5:50:59 PM
>> *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/
>>
>>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
--
Jim K0XU
jim@rhodesend.net
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|