RTTY
[Top] [All Lists]

Re: [RTTY] [WriteLog] Cursor Advance

To: "RTTY Contesting" <RTTY@contesting.com>
Subject: Re: [RTTY] [WriteLog] Cursor Advance
From: "Gary AL9A" <al9a@mtaonline.net>
Date: Wed, 22 Sep 2010 23:00:05 -0800
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
Mike,

How many programmable keys does your mouse have?  If you have another 
programmable key available set it to Insert.  If you left click on a call in 
Rittyrite and the cursor then jumps to the field after the CALL field hit 
the Insert mouse key first.  It will send the exchange only.  Then hit the 
Enter mouse key to log the call and send the QRZ.  Not exactly what you 
want, but it might work until another fix is available.

73,
Gary AL9A

----- Original Message ----- 
From: "Mike" <k4gmh@arrl.net>
To: "RTTY Contesting" <RTTY@contesting.com>
Sent: September 22, 2010 7:26 AM
Subject: Re: [RTTY] [WriteLog] Cursor Advance


Hello Jay,

Installed 10.79D.  Unfortunately, the AdvanceCursorOnInsert function
doesn't help with resolving my initial request of having WL not move
the cursor over to the next entry position when a call is clicked in
the Rttyrite window with the left mouse button.

On Sun, Aug 22, 2010 at 11:15 AM, WS7I <ws7ik7tj@gmail.com> wrote:
> [Entry]
> AdvanceCursorOnInsert=0
>
> Might change by version as he is working on this Mike in the Beta 
> Versions.
>
> 73 Jay WS7I
>
> On Sat, Aug 21, 2010 at 8:06 PM, Mike <k4gmh@arrl.net> wrote:
>> Hello,
>>
>> Would like to have WL not advance the cursor "to the first field in the
>> exchange." when a call in Rttryrite window is click with the left mouse
>> button and placed in the Call entry field. Cannot find anything in WL 
>> Help
>> as to how to adjust the WL.ini file to keep the cursor from advancing
>> although I may have overlook the information. Anyone know of a solution?
>>
>> The reason for wanting this seemingly step back in logging S/W is when 
>> using
>> "Enter sends exch/QRZ" and hitting enter then sends the TU message 
>> instead
>> of the exchange message due to the cursor not being in the Call entry
>> position. Instead have to hit F2 which is aggravating when using a multi
>> key mouse with one of the key's programed as "Enter".
>>
>> 73,
>> Mike, K4GMH
>> _______________________________________________
>> WriteLog mailing list
>> WriteLog@contesting.com
>> http://lists.contesting.com/mailman/listinfo/writelog
>> WriteLog on the web: http://www.writelog.com/
>>
>
>
>
> --
> Jay WS7I
>



-- 
73,
Mike, K4GMH
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty 

_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

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