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

[New Feature] fixed size of time trace window #92

Open
Maabur opened this issue Aug 30, 2023 · 3 comments
Open

[New Feature] fixed size of time trace window #92

Maabur opened this issue Aug 30, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@Maabur
Copy link
Contributor

Maabur commented Aug 30, 2023

Feature Description

The size of the time trace window should stay the same despite the counts displayed. At the moment when the counts changes, the size of the windows slightly increases.

Related Problem

No response

Considered Alternatives

The font size or the number of digits after the dot could be adjusted instead of changing the size of the window automatically.

Additional Context

No response

Contact Details

No response

@Maabur Maabur added the enhancement New feature or request label Aug 30, 2023
@Neverhorst
Copy link
Member

Hi @Maabur , could you elaborate a bit more please? What exactly is changing and when? The window (the GUI) itself should not change at all. Are you referring to the default auto-scaling of the data plot?

@Maabur
Copy link
Contributor Author

Maabur commented Nov 10, 2023

Hello @Neverhorst I will test again with the latest version to see if this problem is happening again. As far as I remember the window (the GUI) is changing. I made the window quite small (less than 1/4 of a 1080p screen) with low counts and then once I reach millions of counts the timetrace windows increases a bit. The fontsize does not changes. I think the window just increases to compensate the increase of the number of digits.

@timoML
Copy link
Contributor

timoML commented Jan 29, 2024

We discussed that the increasing window size is desired behavior for some applications. Thus, we tend to leave it this way and close the issue. Is that ok with you @Maabur? If it's creating bigger trouble, we can discuss a change in behavior in one of the next meetings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants