Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Good\s+Observations\s+in\s+RTTY\s+RU\s*$/: 25 ]

Total 25 documents matching your query.

1. [RTTY] Good Observations in RTTY RU (score: 1)
Author: Steve **KT0DX** <kt0dx@comcast.net>
Date: Tue, 06 Jan 2009 01:01:31 +0000
After every contest we always see all the things that others did wrong. None of them are new if you have at least one RTTY RU under your belt. What I would like to see is things that you noticed that
/archives//html/RTTY/2009-01/msg00161.html (9,420 bytes)

2. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "Alex" <kr1st@amsat.org>
Date: Mon, 5 Jan 2009 20:33:54 -0500
The extra space is a good suggestion. I add the extra space to my call, too, although quite a number of folks logged me as KR1S instead of KR1ST. Both calls are in the master call database and both a
/archives//html/RTTY/2009-01/msg00174.html (9,219 bytes)

3. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "Dick-w0raa" <w0raa@comcast.net>
Date: Mon, 5 Jan 2009 20:34:07 -0700
I agree with what you say, Steve. Especially the comment about sending your own call at the end of the report you send the other station. I had stations send me the following: W0RAA 599 AL AL W0RAA.
/archives//html/RTTY/2009-01/msg00183.html (12,862 bytes)

4. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "Dave Hachadorian" <K6LL@ARRL.net>
Date: Mon, 05 Jan 2009 20:04:08 -0800
Absolutely correct! In fact, Writelog requires TWO spaces after a callsign to correctly identify and highlight it. Since there are so many people using Writelog for RTTY, I would put TWO spaces after
/archives//html/RTTY/2009-01/msg00184.html (11,511 bytes)

5. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "Jim W7RY" <w7ry@arrl.net>
Date: Mon, 5 Jan 2009 20:10:23 -0800
Why not simply add ONE carriage return or line feed after your call into your macro? _______________________________________________ RTTY mailing list RTTY@contesting.com http://lists.contesting.com/
/archives//html/RTTY/2009-01/msg00185.html (12,560 bytes)

6. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "Tom Osborne" <w7why@verizon.net>
Date: Mon, 05 Jan 2009 20:12:40 -0800
Actually, that is the way I think the macro should be set up. If 3 or 4 stations are calling you, and who you come back gets covered up, if you send 'W7WHY 599 CO W0RAA' the other stations on freque
/archives//html/RTTY/2009-01/msg00186.html (9,411 bytes)

7. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "Bill, W6WRT" <dezrat1242@yahoo.com>
Date: Mon, 05 Jan 2009 20:27:40 -0800
ORIGINAL MESSAGE: REPLY: Maybe, maybe not. I send it that way because often there are two or more stations calling me and I want to be sure everyone knows which one I am sending it to. If I send your
/archives//html/RTTY/2009-01/msg00187.html (9,846 bytes)

8. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: Kok Chen <chen@mac.com>
Date: Mon, 05 Jan 2009 20:31:05 -0800
Because it causes the text with the call sign to jump at the recipient's screen just when they are trying to click on it. That is why many people recommend no newline at the end of sending call signs
/archives//html/RTTY/2009-01/msg00188.html (9,334 bytes)

9. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "Bill, W6WRT" <dezrat1242@yahoo.com>
Date: Mon, 05 Jan 2009 20:33:52 -0800
ORIGINAL MESSAGE: REPLY: Because any carriage return makes the print scroll up the screen just as the receiving station is trying to click on it. Very annoying. You should use a <space> at the end, b
/archives//html/RTTY/2009-01/msg00189.html (9,362 bytes)

10. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "Bill, W6WRT" <dezrat1242@yahoo.com>
Date: Mon, 05 Jan 2009 20:46:48 -0800
ORIGINAL MESSAGE: REPLY: My first reaction was "very nice", but then I got to thinking... you do want a newline at the start of a macro to prevent word wrapping right in the middle, don't you? Or can
/archives//html/RTTY/2009-01/msg00190.html (9,472 bytes)

11. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: Kok Chen <chen@mac.com>
Date: Mon, 05 Jan 2009 20:52:31 -0800
With the Cocoa framework of Mac OS X, a text view dynamically creates line breaks when a word extends beyond a line, so a word is never chopped in the middle, unless the word is longer than the line
/archives//html/RTTY/2009-01/msg00191.html (9,334 bytes)

12. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "Dave Hachadorian" <K6LL@ARRL.net>
Date: Mon, 05 Jan 2009 20:53:26 -0800
-- Because a lot of contesters are using N1MM or WF1B logging programs. With these programs, linefeeds cause your callsign to jump up from under the mouse pointer, just as people are about to click.
/archives//html/RTTY/2009-01/msg00192.html (9,092 bytes)

13. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: Phil Sauvey <akdxer@yahoo.com>
Date: Mon, 5 Jan 2009 20:53:42 -0800 (PST)
I think both you and Tom, W7WHY have valid points, Bill from my angle anyhow. I have found that it works best for me putting the station I'm working callsign on both the front and back. As mentioned,
/archives//html/RTTY/2009-01/msg00193.html (11,957 bytes)

14. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: Art Searle W2NRA <w2nra@optonline.net>
Date: Tue, 06 Jan 2009 05:39:44 -0500
Better yet, with N1MM Logger the Grab command also eliminates the scrolling problem. No need to mouse at all. Hitting the "INSERT" key grabs the last call printed and calls that station. I have a {GR
/archives//html/RTTY/2009-01/msg00200.html (9,565 bytes)

15. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "WS7I" <ws7i@ewarg.org>
Date: Tue, 6 Jan 2009 07:19:42 -0800
That is a great solution, Chen, the either or method, either fix it or ignore it for contesting. I like it! Now if you would just send me a Mac! _______________________________________________ RTTY m
/archives//html/RTTY/2009-01/msg00206.html (8,339 bytes)

16. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "WS7I" <ws7i@ewarg.org>
Date: Tue, 6 Jan 2009 07:47:27 -0800
Writelog has always had the grab as well. Looks like Chen is ahead of the game with selection in the software. Writelog always has worked. WF1B I still have a copy of but haven't used it in years! It
/archives//html/RTTY/2009-01/msg00207.html (9,139 bytes)

17. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "Junior" <charlesw_anderso@bellsouth.net>
Date: Tue, 06 Jan 2009 07:57:52 -0800
But what did they do in the early days of contesting on the old machines. I suspect they did not worry about lf, cr, sp , bs ( that's back scrolling ) call grabbing etc. Probably hoping the carriage
/archives//html/RTTY/2009-01/msg00208.html (9,984 bytes)

18. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "Bill, W6WRT" <dezrat1242@yahoo.com>
Date: Tue, 06 Jan 2009 08:33:36 -0800
ORIGINAL MESSAGE: REPLY: Yes, I understand that but I was thinking of the LINE-cut-in-two problem. It's nice to have the other stations exchange always start on a new line so I can follow the text wi
/archives//html/RTTY/2009-01/msg00212.html (10,237 bytes)

19. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "Bill, W6WRT" <dezrat1242@yahoo.com>
Date: Tue, 06 Jan 2009 08:35:29 -0800
ORIGINAL MESSAGE: REPLY: Yes, the "grab" function is great but you still have to click the exchange and that's where the scrolling problem shows up. Bill, W6WRT ______________________________________
/archives//html/RTTY/2009-01/msg00213.html (9,303 bytes)

20. Re: [RTTY] Good Observations in RTTY RU (score: 1)
Author: "WS7I" <ws7i@ewarg.org>
Date: Tue, 6 Jan 2009 08:52:12 -0800
Not sure about N1MM as I haven't mastered that yet but that certainly isn't the case with Writelog Bill, you just hit the Insert Key and it "grabs" the call and moves it to the exchange window. It ha
/archives//html/RTTY/2009-01/msg00214.html (7,905 bytes)

Current List: 1 - 20
Page: [1] [2]
This search system is powered by Namazu