<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hi Larry,<br>
<br>
</div>
<blockquote type="cite"
cite="mid:88c8dd38-2857-8fb6-3fc3-2e39a8caccfd@free.fr">Just to be
clear, when you're talking about the "S&P mode", you mean it
was set by the Ctrl-Tab action, right ?
<br>
</blockquote>
Right.<br>
<br>
<blockquote type="cite"
cite="mid:88c8dd38-2857-8fb6-3fc3-2e39a8caccfd@free.fr">
I think that using a text-command *only* is not desirable. There
must be some sort of "indicator" to know if it's enabled or not,
and a checkmark in the appropriate menu item line does this job.
<br>
</blockquote>
That would be also a good solution, of course. Maybe the feature
will not get a shortcut to prevent turnig it on by hitting this
shortcut accidently.<br>
<br>
<blockquote type="cite"
cite="mid:88c8dd38-2857-8fb6-3fc3-2e39a8caccfd@free.fr">
Also, I'm wondering if a small message (ex "FY5KE spotted") in the
status line (under the log) would be useful as well. It would be a
reminder that the feature is enabled, and inform the user on the
sent spots.
<br>
</blockquote>
I fully agree to that.<br>
<br>
<blockquote type="cite"
cite="mid:88c8dd38-2857-8fb6-3fc3-2e39a8caccfd@free.fr">
Finally, if a F1 hit disables the feature (assuming you're in
S&P mode), what action would re-enables it ?
<br>
</blockquote>
Good question. Maybe F4, sending <mycall>?<br>
<br>
73,<br>
Lenz - DL8RDL<br>
</body>
</html>