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

[Rob Frohne]

Hi Everyone,

I did a little poking around and looking at the issues involved here,
and I need some advice from those more sage than I when it comes to
programming.  The problem is that in cwdaemon, letters are cued to
unixcw as fast as they come in.  Once they are cued, they cannot be
recalled easily, it appears.    

What we want I believe is a message from unixcw when a character is
about to be finished, (maybe when it just finished the last sound of a
character) at which time we can cue another character with unixcw.  In
another thread in cwdaemon, we maintain the buffer that can be edited.  

Is this the best way to do this?  Another way would be to assume that
the speed is correct, and do a calculation that tells cwdaemon how long
to wait until it sends the next character.  I am tempted to do this
because I think I have a much better idea how to do it, though it may
not be as accurate as I would like.

What advice does everyone have for me?

Thanks & 73,

Rob, KL7NA

On Sun, 2007-09-02 at 08:18 -0700, Rob Frohne wrote:
> Hi Joop, et. al.,
> 
> Before I go looking into a fix, I thought I would ask if anyone else has
> looked into the annoyance that bothered me this morning when I got on
> CW.  I was using the Keyer in Xlog, and since I am a poor typist, I made
> a number of mistakes, so I backspaced over them and corrected my errors
> well before the CW was sent.  The corrections were not sent correctly.
> It seems like it sent something for every character I sent, even the
> ones I backspaced over and maybe something for the backspaces.  I
> suspect maybe Xlog is using cwdaemon, and the problem may be in the
> interface between the two.  Anybody have any info on this annoying
> behavior?
> 
> Thanks & 73,
> 
> Rob, KL7NA
> 
> 
> 
> 
> _______________________________________________
> Xlog-discussion mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/xlog-discussion