Hi Jim, Nate and Zoli, we should keep in mind to integrate it in the flow of the qso, especially in contests.
What I mean is running in CQ mode I need the RST of the other station *before* answering his call and will get his RST in his reply. Running in S&P I would first get my RST from him and only *afterwards* need his RST for my reply. Another question is if the operator uses ESM or not. 73, Tom Am Mon, 27 Jan 2020 20:52:46 +0100 schrieb Csahok Zoltan <ha5...@freemail.hu>: > Hi Nate, > > Everything is possible. :-) > > An option I see could be making the exchange box wider to span the > RST fields and let the user input the values. Optionally pre-fill > with 599/59. Then upon storing the qso we would parse the first 2 > words and store them as RSTs. > > A bit tedious for the user to fill and navigate within the exchange > field, but I assume these use cases are not focused on high Q rates. > > > 73, > Zoli > > > On Sun, Jan 26, 2020 at 06:26:36PM -0600, Nate Bargmann wrote: > > * On 2020 26 Jan 15:45 -0600, jim smith wrote: > > > First, I know there is the CHANGE_RST directive, but for QRP > > > contests (at least in the states), many times ops send an actual > > > RST -- 33N, 439, etc. Is there any way to incorporate this in > > > both the received stations data (I imagine it would be in the > > > exchange field, like a serial number) and for the sending > > > station? > > > > > > It would be helpful the above mentioned QRP contests, general > > > ragchews and for SOTA operations as well. > > > > I have seen other loggers handle this so that in the case of Tlf, > > Space would move the cursor from Call to the Exchange/Comment field > > and Tab would cycle through all fields, i.e., Call-->RX RST-->TX > > RST-->Exch-->Call, etc. > > > > As it is now, Space jumps from Call to Exch and then Tab must be > > used to go back to Call as Exch can contain spaces to separate > > exchange elements in some events. Loggers such as N1MM+ create > > additional field entry boxes depending on the event and Space is > > not allowed in any of them so it can be used as a "smart tab" that > > jumps over RST fields, if present, and through all the other fields. > > > > The way Tlf is structured, it would take a lot to have separate > > exchange fields, but it seems as though having Tab cycle through > > all the fields could be doable. As I see it, when Tab enters an > > RST field it could place the cursor under the first '9' and from > > there the field edited as needed. I'm afraid I don't have the time > > to code it for some months so maybe someone else can pick up the > > idea if it is thought to be a good one and add it. > > > > 73, Nate > > -- "Do what is needful!" Ursula LeGuin: Earthsea --