<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I have to agree with Bob's view of the desirable implementation, I have
used ESM for a considerable time with the program SD (Super Duper). I
would not be happy with the idea of abandoning ESM to deal with repeats
- seems clumsy to me.<br>
73<br>
Alex<br>
<pre class="moz-signature" cols="72">~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Remember......... Its just a HOBBY!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</pre>
<br>
<br>
Bob Henderson wrote:
<blockquote
cite="mid:bd0bf46b0907140504o641737ddk3a7a26104fd238c@mail.gmail.com"
type="cite">Hi Philippe<br>
<div class="gmail_quote"><br>
No offence taken but I'd like to make a correction to your
understanding. I make suggestions NOT demands.<br>
<br>
I'm puzzled by your comment. " IMHO, I want to know, every time I
press the 'enter' key, what will be output." This is exactly my point
No. 2. It is not possible to know from looking at the screen what will
be output as it is dependent upon number of 'enter' key presses not the
cursor position.<br>
<br>
The change I have requested would ensure the operator can always know
what will happen next by checking the cursor position on the screen.
This would be true in both RUN and S&P modes.<br>
<br>
I disagree that ESM cannot be useful in S&P. I also disagree that
it is desirable to have to abandon it when repeats are requested.<br>
<br>
With the scheme I have described 99%+ Qs can be handled with use of
only the 'enter' key and Space Bar. With the current arrangement the %
of Qs which can be handled this way is significantly lower.<br>
<br>
I firmly believe my suggestion would make for a superior ESM
implementation. I also accept if I am the only one that thinks so it
would make no sense to implement the change.<br>
<br>
FWIW<br>
<br>
Bob, 5B4AGN<br>
<br>
<div class="gmail_quote">2009/7/14 F6IFY Philippe <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:f6ify@free.fr" target="_blank">f6ify@free.fr</a>></span>
<div>
<div class="h5"><br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi
Bob and all the list,<br>
<br>
No offense Bob, but I hope Olivier and Larry will not follow your
demand.<br>
IMHO, I want to know, every time I press the "enter" Key, what will be
the output.<br>
So when I have a doubt I wish to be able to use the Fx keys to be sure
not sending the wrong message.<br>
<br>
So, I hope Larry will keep the ESM as simple and stupid as it is for
the moment.<br>
IMHO, ESM is useful only in Run mode when all is "nominal" (regular?).<br>
<br>
I have used ESM intensively on others softwares, and I think the
Larry's design is by far the best.<br>
<br>
73<br>
Philippe - F6IFY<br>
<br>
----- "Bob Henderson" <<a moz-do-not-send="true"
href="mailto:bob@5b4agn.net" target="_blank">bob@5b4agn.net</a>> a
écrit :<br>
<div><br>
> Dear Olivier and Laurent<br>
><br>
><br>
> I realise you have only just implemented ESM in V4 but I wonder if
you<br>
> might be prepared to consider a change to its functionality to<br>
> accommodate cursor addressing?<br>
><br>
> The current functionality has two clear disadvantages IMHO:<br>
><br>
> 1. When a QSO does not follow the usual format it is necessary to<br>
> revert to F keys to avoid inappropriate responses. (E.g a request
for<br>
> repeat of exchange.)<br>
><br>
> 2. The operator cannot tell from looking at the screen what will<br>
> happen when he next presses return.<br>
><br>
> If ESM was re-coded such that message sent and logging action taken<br>
> were dependent upon which field the cursor is in, together with the<br>
> content of that field, these disadvantages would be overcome.<br>
><br>
> I believe the following behaviour would provide a useful
improvement.<br>
><br>
> RUN<br>
><br>
> Cursor in empty Call field - return = F4<br>
> Cursor & Call in Call field - return = Insert<br>
> Cursor in Exchange field - return = +<br>
><br>
> S&P<br>
><br>
> Cursor in empty Call field - return = F4<br>
> Cursor & Call in Call field - return = F4<br>
> Cursor in Exchange field - return = Insert<br>
><br>
</div>
<div>> A useful addition to the message variables might be
something like $>.<br>
> This variable added to the end of the RUN Insert message would<br>
> automatically advance the cursor to the Exchange field. The Space
Bar<br>
> toggles between Call & Exchange fields, so it would only be
necessary<br>
> to press the Space Bar before Return on those occasions where a
repeat<br>
> was requested.<br>
><br>
</div>
<div>> Thank you for your consideration.<br>
><br>
> Bob, 5B4AGN, P3F<br>
><br>
><br>
</div>
<div>
<div>> _______________________________________________<br>
> Support mailing list<br>
> <a moz-do-not-send="true" href="mailto:Support@win-test.com"
target="_blank">Support@win-test.com</a><br>
> <a moz-do-not-send="true"
href="http://www.f5mzn.org/cgi-bin/mailman/listinfo/support"
target="_blank">http://www.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
_______________________________________________<br>
Support mailing list<br>
<a moz-do-not-send="true" href="mailto:Support@win-test.com"
target="_blank">Support@win-test.com</a><br>
<a moz-do-not-send="true"
href="http://www.f5mzn.org/cgi-bin/mailman/listinfo/support"
target="_blank">http://www.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<br>
</div>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Support mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Support@win-test.com">Support@win-test.com</a>
<a class="moz-txt-link-freetext" href="http://www.f5mzn.org/cgi-bin/mailman/listinfo/support">http://www.f5mzn.org/cgi-bin/mailman/listinfo/support</a>
</pre>
</blockquote>
</body>
</html>