Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S-parameter Viewer: More fixes #1009

Merged
merged 9 commits into from
Oct 23, 2024
Merged

Conversation

andresmmera
Copy link
Contributor

After more extensive testing, the following issues were spotted:

  • The tool crashed if a session file was loaded when the tool had traces on the display.
  • Load session feature: It had problems to keep the axes settings if the lock setting was enabled.
  • Typo: Put the frequency units between parentheses.
  • The limit widgets include a QFrame as a separator in order to clearly distinguish the widgets associated with a certain limit. This separator was not being removed when a limit was deleted.
  • There was a problem with the marker/limit/trace lists: When the user removed a marker, the other widgets were not rearranged so the next time the user added a new marker/limit/trace, the new widgets overlapped the old ones.

All these problems have been fixed in this PR.

In addition, a global offset limit has been added. This allows the user to adjust all the limit lines in a row, and is very useful when you need to adjust a mask with a number of limit lines. As far as I know, (at least) the Keysight network analyzers have this feature.

It is quite weird to have this button checkable. It gives the feeling that the GUI is frozen.
Before loading a session file it is needed to clear the current dataset and traces.
It was found that before this commit the program had problems to load session files. Specifically, it didn't catch the axes limit and it also had problems if the previous session was saved with the lock status = true
It was found that when a limit was removed, the separator related to it stayed there. This commit fixes this.
It was found that after a trace/limit/marker is removed, if the user adds a new trace/limit/marker, the new widgets overlap the last ones. 

This happened because the position of the widgets in the QGridLayoyt were not updated after a trace/limit/marker is removed.

This commit addresses this issue.
It was added an offset feature to move all the limits on a row.
@andresmmera
Copy link
Contributor Author

@ra3xdh Please wait until tomorrow evening to merge this. I would like to try the Windows artifact.

@ra3xdh ra3xdh added this to the 24.4.0 milestone Oct 20, 2024
@ra3xdh ra3xdh added the tools label Oct 20, 2024
Now when the user adds a marker, the program adds a little text at the top of the marker line indicating the frequency.
@ra3xdh
Copy link
Owner

ra3xdh commented Oct 23, 2024

Is this PR ready for merge now?

@andresmmera
Copy link
Contributor Author

Yes, it's ready.
If I find any more bugs, I will open another PR.

@ra3xdh ra3xdh merged commit 8fc712e into ra3xdh:current Oct 23, 2024
7 checks passed
@ra3xdh
Copy link
Owner

ra3xdh commented Oct 23, 2024

Merged.

@andresmmera andresmmera deleted the SPAR_Viewer_Fixes branch October 23, 2024 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants