Hi Again:
Thinking again about this thing, best explanation ContestLog file got
corrupted probably at entry 26 and that affected no more QSO were being
logged. Yes, there was something I remember happening with the popup QSO
window where garbage from PPT was received at one of the fields. Have
c
Yes, I am (attached). Not a biggie, I deleted and recreated that log entry
again with the correct band. I suspect it got confused because I had 40M
selected in the main program, even thouth I entered 20m in the log pop-up. It
came out correct after put WSJT-X back on 20. Except for the time, th
Hi:
Forgot to tell (previous post) those recent QSO were using TAB1.
Edfel
KP4AJ
On Sat, Dec 1, 2018 at 10:08 PM Edfel Rivera wrote:
> Hi All:
>
> Well, after editing the 569 0064 to 569 FL (row 26) QSO are logging again
> and nicely. What was the problem, not sure but Recevd 569 0064 was the
Hi All:
Well, after editing the 569 0064 to 569 FL (row 26) QSO are logging again
and nicely. What was the problem, not sure but Recevd 569 0064 was the
only thing I changed to get the QSO saving again. See below. QSO time
reflects how long this issue interrupted QSO logging. BTW, QSO logging n
On 02/12/2018 02:52, Jim Shorney wrote:
I manually created a log entry and it accepted it this time. Now, however, I am
trying to correct the hand in the log to 20m, but 20m does not show up on the
selection list when on that line. In fact, it only seems to show up on the list
for entries that
That seems to have been the problem with my WL7CG contact. I manually created a
log entry and it accepted it this time. Now, however, I am trying to correct
the hand in the log to 20m, but 20m does not show up on the selection list when
on that line. In fact, it only seems to show up on the li
Hi:
Well, this is nonsense. After editing last recorded QSO which received
column was 569 0064 for LW5DR . I changed to FL just to test. Be assured
I didn't edited that file in anyway before trying this. After that QSO were
again saved. I have worked:
023330 -24 0.1 1564 ~ KP4AJ MI0LLG RR73
Hi Edfel,
sorry I was not clear. The edits I am referring to are to the Contest
Log window rows. As it stands in WSJT-X v2.0.0 RC5 edits to fields in
the Contest Log window table are not committed until you change the
focus to another row. Until you do that pending edits will block the
additi
Hi Bill:
I filled those fields (operator, name) because fields were empty (not
populated by the program) and because program pop up message was Invalid
QSO. Was a way to test if that empty fields were the reason for the error.
Anyway, Invalid QSO popups keeps happening and they are empty at those
Hi JIm:
Yes, I tried that too. Name is not more there long ago.
Thanks!
Edfel
KP4AJ
On Sat, Dec 1, 2018 at 8:57 PM Jim Shorney wrote:
>
> I don't know if there is any kind of check on the Operator field for
> something that looks like a valid call, but you may want to put your call
> in the
Hi Edfel,
I am fairly certain that the logging lockout when al the required fields
are populated is related to unsaved edits to the contest log window. As
it stands you have to move to another row to commit any edits, then you
can log a new row.
I am surprised how many reports of this there
I don't know if there is any kind of check on the Operator field for something
that looks like a valid call, but you may want to put your call in there
anyway. Having your name in there is bound to confuse some software
somewhere... :)
73
-Jim
NU0C
On Sat, 1 Dec 2018 20:41:37 -0500
Edfel R
Hi Jim:
See the another popup window 'Invalid QSO' below, at capture you are
refering, I tried placing my name in Operator to see if having that field
blank was the problem. There are also others with similar problem:
https://mail.google.com/mail/u/0/#inbox/QgrcJHrjBQfqKcQGxpzNBkSHmpVzzlKMjDV
7
I wonder if it does not like that you have your name in the OPERATOR field
instead of your callsign. AFAIK the ADIF field that this maps to is for
operator call, which CAN be different from the station call under certain
circumstances.
73
-Jim
NU0C
On Sat, 1 Dec 2018 17:32:38 -0500
Edfel Rive
Hi:
QSO below was refused to Log into ContestLog. ContestLog have 26 entries
also other QSO after that was logged. Not sure why but had to cancel
logging of N5OK QSO.
Thanks.
73'
Edfel
KP4AJ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.ne
15 matches
Mail list logo
