I believe it can be done with Qt using IntValidator on the TextBox input?
Alan G0TLK
On 21/10/2022 10:19, Frode Igland via wsjt-devel wrote:
Roman,
I see your point. Since the power data is manually input in the
logging window, I guess that the check for "numbers only" in the "Tx
Power"
Roman,
I see your point. Since the power data is manually input in the logging
window, I guess that the check for "numbers only" in the "Tx Power" field
must be made in the logging window, before the "OK" is accepted. However,
I don't know if this check can be easily implemented. In the
Laurie,
Yes, I use JTAlert, but not for logging. The logging data are sent directly
from WSJT-X to HRD Logbook, which apparently does the same alpha character
stripping as JTAlert. On the next session start, I let JTAlert scan the
database, to have the alerts working properly.
(Outside Roman's
On 20/10/2022 12:05 am, Frode Igland via wsjt-devel wrote:
I have used the "Tx power" field in the WSJT-X logging window for most
of my tens of thousands of WSJT-X QSOs. Whether I enter "40 W", "40W"
or "40", it hits my HRD Logbook as "40
Frode,
I recall that you are using JTAlert, is
Hi Frode
I agree with you that in practice many
applications are tolerant and read non-compliant
ADIF files without errors. However, my report was
actually triggered by a practical problem.
Concretely, I tried to read the ADIF file created
by WSJT-X using the Python library "hamutils".
Hi, Roman.
My experience is that the ADIF format accepts more than the ADIF
specifications may indicate. I have used the "Tx power" field in the WSJT-X
logging window for most of my tens of thousands of WSJT-X QSOs. Whether I
enter "40 W", "40W" or "40", it hits my HRD Logbook as "40", i.e. a
Hi
I would like to report an issue with the ADIF log
created by WSJT-X. I'm currently using v2.5.4 on
macOS 12.6.
WSJT-X offers to log QSOs by filling in a form
prompt. One of the fields of the form allows to
log the "Tx power". Apparently, the form accepts
any text string entered into
