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

Trigger properties update for every digit entered #475

Closed
dan-gies opened this issue Aug 22, 2022 · 3 comments
Closed

Trigger properties update for every digit entered #475

dan-gies opened this issue Aug 22, 2022 · 3 comments
Labels
ui New UI features

Comments

@dan-gies
Copy link

dan-gies commented Aug 22, 2022

System Info:

Glscopeclient version: 0.1-0ec5f20
OS: Windows 10
Oscilloscope: Siglent SDS6204A

Description:

In the trigger properties dialog, the trigger updates live on the scope as I enter it into the "Level" field, instead of on dialog close (or, preferably, on "ENTER" or "OK" button, if one existed).

Example: I want to enter 150mV trigger. I type "1", trigger is set to 1V on scope. I then type "5", trigger is set to 15V, which is outside of trigger limit. I type "0" then "m" and trigger is correctly set.

I don't think this poses a risk to the instrument, but it isn't how I expected the UI to function.

@azonenberg
Copy link
Collaborator

We're trying to move to a more modeless/nonblocking UI flow so that changes occur live rather than waiting for you to close the dialog (so you can leave it open and tweak trigger settings, seeing the scope update in real time).

Maybe it would make more sense to trigger the push when you shift focus outside the text box rather than immediately on key presses? Open to discussion.

@azonenberg azonenberg added the ui New UI features label Aug 22, 2022
@dan-gies
Copy link
Author

I like the idea of triggering the push when you shift focus to a different text field, or on hitting ENTER.

@azonenberg
Copy link
Collaborator

Wontfix in glscopeclient. The new behavior is implemented in ngscopeclient.

@azonenberg azonenberg closed this as not planned Won't fix, can't repro, duplicate, stale Oct 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ui New UI features
Projects
None yet
Development

No branches or pull requests

2 participants