开云体育

Hi Bo,
now I've gotten to your long list of ideas! Thanks for providing them!

Screenshot/image saving is definitely interesting! Currently, the
graphs/plots are all painted directly on a Qt widget, so I would have to
find something that could save those. I think it should be possible, though.

Exporting a general frequency/amplitude (or even amplitude/frequency) file
shouldn't be much of an issue. But, maybe it relates to your next
suggestion: The auto markers for filters. I'd *love* to do that! My biggest
issue is finding a way to 1) identify the filter, 2) find out what the
passband is, and what the passband level/ripple is, and then identify the
3dB/10dB etc. points. The latter part, finding the points, is "easy". What
worries me is the first part :-)

The marker architecture is fully set up to allow for more than 3 markers -
but to fit in 1366x768, it's currently limited to 3. I think I'll add it as
a setting so you can have more. :-)

Thicker trace lines should be an easy setting to make.

The cosmetic points are all sensible, and I'll endeavour to have them
included soon! The only exception is the COM port bit: The current
functionality already finds the correct device if possible, so a dropdown
menu would only really be required if you have more than 1 NanoVNA
connected... I don't think I'll present the users with devices that the
software can't identify as compatible, for now at least, but maybe the
connection functionality needs an overhaul at some point.

Segments: This was previously called sweep count, and is really the base
functionality of the software, the sole reason I wrote it: It refers to how
many segments the sweep span is broken into, each of 101 sample points, in
order to increase resolution over the default the NanoVNA provides. So
putting in 10 provides 1010 points, 50 gives 5050 points, etc. The label
next to it presents the distance between each data point, as that's proven
useful for me, at least. Hz/step is my term for the number of Hz between
two data points .. maybe that's just my own terminology bleeding through, I
don't know. I'm open to suggestions :-)

Thanks again for taking the time to write out all these suggestions!
--
Rune / 5Q5R