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

Triggered Data Graph misbehaving #1283

Open
mengstr opened this issue Apr 22, 2024 · 0 comments
Open

Triggered Data Graph misbehaving #1283

mengstr opened this issue Apr 22, 2024 · 0 comments

Comments

@mengstr
Copy link

mengstr commented Apr 22, 2024

Below is small test design to demonstrate the issue I have.

The first shows the problem - If I start the clock by activating the "enable toggle" the scope screens clears, then another scope screen appears and hides repeatedly slowing down the run to a crawl. And after a while the graph is displayed the original window. But it records far less than the set amount of samples. And it will not add anything more even if I disable the clock and then manually clicks it with the push button.

This happens regardless of of the scope screen is closed at start of if it's already there from a previous run.

The second movie show me first adding a few manual clock ticks into the graph, then I start the freerunning mode. Then the scope graph is continuously updated and it has no problems recording up to the set amount of samples.

I've added the dig-file for your convenience. This is running the latest pre-release on a Macbook.

mats@Matss-MacBook-Pro hm-admin % java --version
openjdk 17.0.2 2022-01-18
OpenJDK Runtime Environment Temurin-17.0.2+8 (build 17.0.2+8)
OpenJDK 64-Bit Server VM Temurin-17.0.2+8 (build 17.0.2+8, mixed mode)

StartWithContinous.mov
SingleStepBeforeContinuous.mov

FlashyScopeTest.dig.zip

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

No branches or pull requests

1 participant