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

[Joop Stakenborg]

Op maandag 03-09-2007 om 12:56 uur [tijdzone -0700], schreef Rob Frohne:
> Hi Tomi,
> 
> I did a bit more looking into this, and it appears that the real issue
> is at the unixcw level.  That program provides routines that will block
> your program until an element is sent, but not for a whole character.
> Perhaps Simon can advise us.
> 

If you want to use backspace, it should be relatively simple to use the
cwdaemon 'echo' feature. This way you can keep track exactly which
characters are sent. You just need to maintain a character counter,
which decreases when backspace is hit.

I don't have any time to look into it now, but this issue has been on my
TODO list for long.... Time lacks. Since I am just a single developer
maintaining several software packages trivial things like this will have
to wait.

> Most of us get around the keying problem by using VOX, but not all rigs
> have that. 
> 
> Yes, cwdaemon uses UDP.  TCP/IP has possible issues with no arrival time
> guaranteed, but that should be minimal with most CW, and network
> connections to localhost. 
> 
> To  me this problem seems like a pretty serious lack for any program
> that actually keys the transmitter.
> 

Use the ESCAPE key within the xlog keyer and transmitting will abort
immediately. You can then retype what was typed wrong...

> 73,
> 
> Rob, KL7NA


Joop PG4I