<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Hi Bob,<br><br>today had time to test ur new version, and everything is as expected, it works fine, i noticed only that if u fill the partner with<br>4 calls, and u pickup them with CTRL 1 to 3 emptying the partner window , the next F12 filling don't start from row 1but from <br>Row 3 and the callsign field is not filled with the last one. the behavior is different from 1st filling that if followed to an ALT TAB<br>or first partner window opening.<br><br>73 de Fabio I4UFH<br><br>Il giorno 30/set/2010, alle ore 04.53, Bob Wilson, N6TV ha scritto:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Wed, Sep 29, 2010 at 6:36 AM, Tõnno Vähk <span dir="ltr"><<a href="mailto:Tonno.Vahk@gafm.ee">Tonno.Vahk@gafm.ee</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">The only thing I noticed is that I am using $SPACEBAR and cursor
moves to exchange field after I press INSERT. Now F12, callsign and ENTER
activates another ENTER and cursor moves back to the callsign field. That is
wrong because I need it to stay on exchange field to be able to enter exchange
for the first station.</span></p><div><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span><br class="webkit-block-placeholder"></div><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Can you do so Bob, that ENTER to close StackCalls window is not
double-affecting the ordinary cursor position?</span></p></blockquote></div><br>First, thanks for trying it and for the kind words.<br><br>I believe I have fixed the cursor problem that you reported. Please try the latest StackCalls.zip which you can download from <a href="http://bit.ly/wtscripts">http://bit.ly/wtscripts</a> now.<br>
<br>After running StackCalls (e.g. [F12]), the cursor will now be placed at the <i>end</i> of the callsign or exchange field, wherever it was in at the time that you invoked StackedCalls. This will work OK for CQ WW or other contests with a single exchange field. It will not necessarily put the cursor in the right place for contests with more than one exchange field. I can't make it perfect until new LUA APIs are added by Laurent that will provide a way for a Lua script get and set the exact position of the cursor, or directly store a callsign in the partner window stack, without having to simulate Alt-Enter.<br>
<br>I've also fixed another problem that I noticed. I now make sure that the callsign field, if non-empty, will stay as it is, whether there are zero callsigns in the stack, or several. I had to "borrow" then 9th position in the Partner window to temporarily save the current callsign, so as long as you have 8 or less callsigns stacked, StackCalls should behave as expected.<br>
<br>Please let me know how it goes.<br><br>73,<br>Bob, N6TV<br>
_______________________________________________<br>Support mailing list<br><a href="mailto:Support@win-test.com">Support@win-test.com</a><br><a href="http://www.f5mzn.org/cgi-bin/mailman/listinfo/support">http://www.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br></blockquote></div><br></body></html>