* On 2010 01 Feb 20:47 -0600, Rob Frohne wrote: > The problem I have with cwdaemon is that it wasn't written with editing > in mind. You send a character (and suppose it was a typing error and > you are far ahead in your buffer of what is being sent). You can't > correct it because it has been sent to cwdeamon already, and cwdaemon > only allows you to cancel the whole buffer, not edit it. I looked into > fixing this problem in Xlog, and finally gave up, figuring it would be > much easier to start from scratch and manage the buffer totally in Xlog > and skip cwdaemon.
I'll admit to not having extensive experience with cwdaemon so this is a rather glaring limitation especially when sending directly from the keyboard. For a contest logging program it's a mostly hidden issue and the sent characters are mostly the result of a macro invocation. > Another thing I don't like about cwdaemon is that it grabs your parallel > port, and there have been times I wanted to use the parallel port for > something, but forgot that cwdaemon was running, and it took me a little > time to figure out what was going on. Does it do the same when set to use the serial port? I would assume so. Still, that doesn't mean that the cwdaemon command set is fatally flawed, or does it? By that I mean Fligi or some other program could be a cwdaemon replacement to support the widest possible group of existing software but allow extensions that future software could take advantage of. For the moment Linux logging programs have settled on the cwdaemon interface. Perhaps someone should start a Morse daemon project that addresses cwdeamon's shortcomings. :-) 73, de Nate >> -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Ham radio, Linux, bikes, and more: http://n0nb.us/index.html _______________________________________________ fldigi-alpha mailing list [email protected] https://lists.berlios.de/mailman/listinfo/fldigi-alpha
