A bug due to an unknown conflict with all versions of NanoVNA-Saver

[Ghaz75]

I had an old firmware loaded in my NanoVNA-H and I used new release of NanoVNA-Saver and it was working fine. Then I installed DFUSeDemo and its corresponding STM32080 driver to upgrade the firmware of my NanoVNA-H. I used your NanoVNA.H.v1.2.29.dfu for upgrade.
Since then following error is generated once I run latest or any previous version of NanoVNA Saver from both x86 and x64 binaries. However the device with the above mentioned new firmware works fine with other softwares like NanoVNA-App by OneofEleven and VNASharp etc. NanoVNA-Saver all versions now give same error whether device is connected or not, right at the start and does not load.

Traceback (most recent call last):
File "nanovna-saver.py", line 37, in
File "NanoVNASaver_main_.py", line 95, in main
File "NanoVNASaver\NanoVNASaver.py", line 128, in init
File "NanoVNASaver\Controls\MarkerControl.py", line 46, in init
File "NanoVNASaver\Marker\Widget.py", line 163, in init
File "NanoVNASaver\Marker\Widget.py", line 206, in buildForm
TypeError: object of type 'NoneType' has no len()

It may be possible that DFU app and its driver have conflict with your new firmware.