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

Time Series Reader resets count trace [Bug] #106

Open
NicolasStaudenmaier opened this issue Oct 17, 2023 · 2 comments
Open

Time Series Reader resets count trace [Bug] #106

NicolasStaudenmaier opened this issue Oct 17, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@NicolasStaudenmaier
Copy link
Contributor

Version

current main

What is affected by the bug?

Count trace of the Time Series Reader gets resets and starts a new trace when any of the "Trace settings" fields was clicked and then the active window is changed from the Time Series to any other one (not necessarily Qudi). Whenever the Time Series GUI changes from being the active window to the inactive one the count trace resets unless the trace is stopped and a new one manually started.
Occurs both with dummy configuration and real hardware.

[Windows10]

When does the bug occur?

When changing to any other window, i.e. the Time Series GUI is not the active window anymore.

How do we replicate the issue?

  • Start Time Series GUI and click start "Start trace"
  • click into any of the fields of the Trace settings
  • change to another window

Expected behavior

The count trace should not reset.

Relevant log output

No response

Additional Comments

Not sure whether this is a bug of the graphic packages. Can the Trace settings simply be greyed out and not be selectable while the count trace is acquired? This could solve the issue.

Contact Details

No response

@NicolasStaudenmaier NicolasStaudenmaier added the bug Something isn't working label Oct 17, 2023
@Neverhorst
Copy link
Member

Well, locking the settings during active streaming would resolve this and it is the easiest way, too. But we should discuss if this is desired behavior.

@Neverhorst
Copy link
Member

Discussions revealed that a general locking of the settings during a running measurement is not desired. Ignoring the EditingFinished signal of the spinboxes when changing active window needs to be facilitated in customized event handlers (either of the spinboxes or the main window).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants