Re: [Xlog-discussion] Xlog Keyer Bug....

[Joop Stakenborg]

On Tue, 2007-09-04 at 09:00 -0700, Rob Frohne wrote:
> Hi Joop,
> 
> What echo feature are you talking about in cwdaemon?  Here posted below
> are the commands from cwdaemon's README file:
>         <ESC>"h"<"opt.text">     Cwdaemon replies "h" and optionaly text
>         to logging
>                                  program when playing is done.

ESC"h" is what you need. Tucnak uses this feature. So you send a
character to cwdaemon and the ESC"h" after that. Cwdaemon will then echo
back when the character is done. This way you will always know where you
are, just keep track of the characters typed and the echo's.

I have never used this feature myself, it was designed by Lada, the
author of tucnak. Tucnak should have example code... I don't know how
extensively it is used however...

>         
>         
> Also, the ESCAPE key or STOP button flushes the buffer so that it stops
> at the end of the element (dit or dah) instead of the end of the
> character.  To use that way of editing the buffer will cause errors in
> keying.
> 
> Am I missing something?  I hope so.
> 

This was done deliberately. If you want to stop or abort, you want to do
it right away, even when in the middle of a character. We don't want to
wait for a long CW character to end. I use this feature very often in
contests, I call CQ and just before the CQ starts I hear someone calling
me. If I hit abort I can still copy most of the callsign because only a
dot or dash is transmitted on my side.

> Thanks so much for the help with this.  I know how it is being the only
> developer of a program.  I'm happy to put a fix in for you, but after my
> inspection, it looks like the place it needs to go is unixcw, and then
> changes propagate out from there.  I think the problem is not with Xlog
> or cwdaemon.  I am hoping to hear from Simon.  He may be able to solve
> my dilemma easily.  Or maybe the feature you mention in cwdaemon didn't
> make it into the readme, and my quick perusal of unixcw missed something
> there.
> 

I bet it can easily be solved within xlog. All the features are there
already.

> Thanks again & 73,
> 
> Rob
> 

Regards,
Joop PG4I