WriteLog
[Top] [All Lists]

Re: [WriteLog] % L in rtty F key memory not working

To: <writelog@contesting.com>
Subject: Re: [WriteLog] % L in rtty F key memory not working
From: "Gary AL9A" <al9a@mtaonline.net>
Date: Tue, 22 Jan 2013 12:57:10 -0900
List-post: <writelog@contesting.com">mailto:writelog@contesting.com>
Hi Jim,

Glad to hear %L is now working for you.

To use the call stack first review the Help manual section "Entry Push/Pop Call Queue". There are several things you can do to your writelog.ini file to make manipulation of the stack very easy.

First, create a new section in your writelog.ini file as below:

[RttyContextMenuEntries]
1=PUSHCALL

The default in Rittyrite is if you right click on a call a drop box opens with some default selections. One of these is to Push Call to the stack. If you add the above line to your ini file the drop box goes away as the only option left is PUSHCALL. This now becomes the default of a right mouse click on a call. There is no visible feed back, but the call is added to the stack. If the CALL field is empty you can see the first three calls in the stack just to the left of the CALL box where the next number is usually shown.

Now you need a way to manipulate the stack if necessary. I did this by creating two keyboard shortcut keys, the "[" and "]" keys which were unused for anything else. You can use the Setup/Keyboard Shortcuts... utility in WriteLog or just add the following two lines to your KeyboardShortcuts section in your ini file if you have one.

[KeyboardShortcuts]
OPEN_SQUARE=EntryPopCallFromQueue
CLOSE_SQUARE=EntryPushCallToQueue

These two keys when toggled one after the other will cycle through all the calls in the stack - Pop, Push, Pop, Push, etc. If you have a call you want to delete from the stack just cycle through the stacked calls until the one you want is in the CALL field and then hit Alt+W to wipe it out of the stack. I rarely have more than two or three calls in the stack so it is fairly easy to manage.

I now create two shortcut macros for RTTY use.

F8 - "%R%C TU %L "
F9 - "NOW %C 599 nnn %C "

During a run if I am called by more than one station whose calls print clearly I click on the first call I want and hit Insert. This starts sending my exchange message to him. After hitting Insert, while my exchange is being sent, I right click on the second call to Push the call onto the stack. After my exchange message ends I receive the exchange from the first station and left click the report into the correct fields in the Entry window. When his exchange info to me is ready to log I hit the F8 key followed immediately by the F9 key. This logs the first call and his information, Pops the next call from the stack into the CALL field and sends the combined macro strings together to parse the NOW... message.

Really easy and seamless way to manage the pileup. Give it try and I'm sure you will agree.

73,
Gary AL9A


----- Original Message ----- From: "James Balls" <makidoja@gmail.com>
To: <writelog@contesting.com>
Sent: January 22, 2013 1:28 AM
Subject: Re: [WriteLog] % L in rtty F key memory not working


Hi all

OK got it working now

I'm interested in this statement from Gary



Fn = "%R%C TU %L ", which should  send TU to the current call, log that
call and then pop the next call from the stack into the Call field.


which part of that puts the next call in the stack into the call field

What happens if it's a busted call? just manually edit?

Thanks

Jim M0CKE
_______________________________________________
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: 2013.0.2890 / Virus Database: 2639/6049 - Release Date: 01/21/13


_______________________________________________
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>