A user-definable speed change would be great and would satisfy everyone. This
should not be difficult to implement. I speak from experience, as I
implemented a real-time, interrupt driven, 1 wpm step morse code generator in a
logging software application I wrote several years ago. Bob - W3YY
---------------
In a message dated Thu, 3 Jan 2002 3:14:54 PM Eastern Standard Time, Mark
Beckwith <swca@swbell.net> writes:
>
> Jean Giesler said:
>
> >>I do not see that a change on one WPM would be useful.
>
> and Pete said:
>
> >I share this view.
>
> Both went on to talk about their operating techniques. This was not my
> intent.
> I am sure we all have our things we like and things we don't like. What may
> be
> important to me may not be important to you. More to the point - does anyone
> else think TRlog would be improved if this variable were user-definable like
> so
> many other things are (many of which are of little or no value to me
> personally)?
>
> The question was "is this easy?" If it is easy I would encourage Tree to do
> it.
> If it is hard I would understand why he would not want to. Of course, the
> default should remain 3WPM and the change would be transparent.
>
> I change my sending speed frequently and the technique has served me well. I
> would find more resolution in step size useful. Would anyone else?
>
> Mark, N5OT
>
>
> --
> FAQ on WWW: http://www.contesting.com/FAQ/trlog
> Submissions: trlog@contesting.com
> Administrative requests: trlog-REQUEST@contesting.com
> Problems: owner-trlog@contesting.com
> Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
--
FAQ on WWW: http://www.contesting.com/FAQ/trlog
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|