Hi Bryan,
thanks - I figured it was something like that, but it's nice to have it
confirmed :-) With your description of how you did your calibration, I'm
sure more people will be using these fields - so I will prioritise getting
the input validation done :-)
--
Rune / 5Q5R
On Thu, 17 Oct 2019 at 23:17, bryburns via Groups.Io <bryburns=
[email protected]> wrote:
On Wed, Oct 16, 2019 at 07:55 AM, Rune Broberg wrote:
I hope this helps you find the issue that caused the crash.
Rune,
I just figured out what is causing the crash I referenced above. If a
user leaves one of the text boxes in the "Calibration settings" area blank,
no number at all, nanoVNA-Saver will immediately crash resulting in the
error:
File "NanoVNASaver\Calibration.py", line 447, in calculate
ValueError: could not convert string to float:
I think this means that you need to check all of those boxes to make sure
they have a valid number before actually trying to convert them to a
floating point number.
--
Bryan, WA5VAH