Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+CW\/RTTY\/SSB\s+Messages\.\.\.\.\.\.\.a\s+request\s*$/: 15 ]

Total 15 documents matching your query.

1. [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: "K2MK" <k2mk@comcast.net>
Date: Wed, 24 Dec 2014 14:46:58 -0500
It would be nice if separate CW and RTTY messages could be accessed from the stored message list and have WriteLog pull the correct message as determined by the transmission mode. Much the same way W
/archives//html/WriteLog/2014-12/msg00074.html (7,443 bytes)

2. Re: [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: Clay Melhorn <n9io@hotmail.com>
Date: Wed, 24 Dec 2014 14:30:07 -0600
I totally agree, my daily dxpedition mode logs like most of us can consist of CW SSB and RTTY. It would be a very nice feature instead of having to pull up a prerecorded memory for each mode. Clay N9
/archives//html/WriteLog/2014-12/msg00075.html (8,679 bytes)

3. Re: [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: "Darren Collins (G0TSM)" <daz@g0tsm.com>
Date: Wed, 24 Dec 2014 20:55:51 +0000
I've asked for this before as I use Writelog for SSB/CW/RTTY logging when on holiday. I know there is a work around but that's not the same. The other thing I'd like is to be able to trigger the inte
/archives//html/WriteLog/2014-12/msg00076.html (9,283 bytes)

4. Re: [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: Jim Reisert AD1C <jjreisert@alum.mit.edu>
Date: Sat, 27 Dec 2014 19:00:12 -0700
I would be happy if WriteLog would just ignore the RTTY-specific macros in the CW/SSB/Digi memories (like Tx and Rx). It would make switching between CW and RTTY so much easier. It was a pain when I
/archives//html/WriteLog/2014-12/msg00077.html (7,606 bytes)

5. Re: [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: "Ed Muns" <ed@w0yk.com>
Date: Sat, 27 Dec 2014 21:35:20 -0800
The following comment doesn't directly address your concern, but it describes how I avoid this issue. I save each contest in its own folder along with any other files pertaining to that contest, like
/archives//html/WriteLog/2014-12/msg00078.html (9,023 bytes)

6. Re: [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: "Joe Subich, W4TV" <lists@subich.com>
Date: Sun, 28 Dec 2014 08:29:38 -0500
Over time, though, I have a rich enough archive of old contests, such that I usually have the exact contest from which I can import messages. Thus, I never run into the problem of messages being for
/archives//html/WriteLog/2014-12/msg00079.html (10,709 bytes)

7. Re: [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: Gary Senesac <al9a@mtaonline.net>
Date: Sun, 28 Dec 2014 07:12:08 -0700
Work around for the DXPedition and General DXCC tracking modes for switching between CW and RTTY macros in WL.... Create two "dummy" logs, one containing your CW macros, the other your RTTY macros. T
/archives//html/WriteLog/2014-12/msg00080.html (12,692 bytes)

8. Re: [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: "Joe Subich, W4TV" <w4tv@subich.com>
Date: Sun, 28 Dec 2014 09:43:47 -0500
When you want to change modes just go to Setup/CW/RTTY/SSB memories, Browse to the correct "dummy" log name and import the correct macros for that mode. Then reconfigure the Rttyrite window settings
/archives//html/WriteLog/2014-12/msg00081.html (13,109 bytes)

9. Re: [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: Jim Rhodes <jim@rhodesend.net>
Date: Sun, 28 Dec 2014 09:21:54 -0600
I have yet to see any mention of FKeys. You can set up as many buttons as you need messages in whatever mode. Even include macros to change modes on the rig, although these may need to be assigned to
/archives//html/WriteLog/2014-12/msg00082.html (15,866 bytes)

10. Re: [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: "Ed Muns" <ed@w0yk.com>
Date: Sun, 28 Dec 2014 10:21:24 -0800
Good work-around though not quick for mode-changing. Remember, though, that WriteLog is a contest logger. DXpedition and general logging are not as fully-featured in a contest logger. This is the sam
/archives//html/WriteLog/2014-12/msg00084.html (15,253 bytes)

11. Re: [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: "Ed Muns" <ed@w0yk.com>
Date: Sun, 28 Dec 2014 10:35:50 -0800
The requirement of using a mouse/trackball to click buttons in additional windows on the screen is a non-starter for me. For others, though, this UI may be fine. The last software update was 14 Febru
/archives//html/WriteLog/2014-12/msg00085.html (9,141 bytes)

12. Re: [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: Jim Reisert AD1C <jjreisert@alum.mit.edu>
Date: Tue, 30 Dec 2014 16:04:12 -0700
Operating as a W1AW/# station, where there are hundreds of callers and you are trying to work them as fast and efficiently as possible sure sounds like a contest to me, regardless of the band or mode
/archives//html/WriteLog/2014-12/msg00101.html (9,342 bytes)

13. Re: [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: "Ed Muns" <ed@w0yk.com>
Date: Tue, 30 Dec 2014 23:30:26 -0400
Yes, and I used WriteLog for W1AW/6 just fine. High rates and all. But, I was not changing modes so often that I needed a fancier way of loading messages than what has been suggested. Gary AL9A outli
/archives//html/WriteLog/2014-12/msg00103.html (10,779 bytes)

14. Re: [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: Jeff Stai <wk6i.jeff@gmail.com>
Date: Wed, 31 Dec 2014 12:33:42 -0800
Yes, Gary's method is fine and that's what I have also done. Where it can be problematic is when you are in a multi-op situation with multiple modes and operators with varying level of familiarity wi
/archives//html/WriteLog/2014-12/msg00111.html (9,851 bytes)

15. Re: [WriteLog] CW/RTTY/SSB Messages.......a request (score: 1)
Author: <john@kk9a.com>
Date: Wed, 31 Dec 2014 20:33:28 -0500
John KK9A - P40A Yes, Gary's method is fine and that's what I have also done. Where it can be problematic is when you are in a multi-op situation with multiple modes and operators with varying level
/archives//html/WriteLog/2014-12/msg00112.html (9,683 bytes)


This search system is powered by Namazu