remaining scope curves when paused

It would be super-helpful to have the scopes (Oscope and Logic Analyzer) showning the last curves, when the simulation is paused.
I'm currently stucking in debugging code and try to compare timings. However, sometimes the last curves are shown when paused, sometimes the go flat just when I try to measure.

It would be super-helpful to have the scopes (Oscope and Logic Analyzer) showning the last curves, when the simulation is paused.

Not sure if I'm understanding you...
As far as I know this is how it is working now in version 1.0.0.
Not only you can see the wave, but go back and forth, and use it normally.
Logic Analizer has the extra feature that you can move the wave with the mouse:



If it's not this what you mean or if it's not working for you, please let me know.

Yes that exactly what it should be, but it does not work
It seems to be a problem on the WIN 1.0.0 version..

That's weird...
Windows version is also working for me, at least in Wine.

And right now I can't imagine anything that can cause this.
Does it always happen, with all circuits?
Can you try with the same circuits I used in the video?
DS1307 example is in tester version 768.

I activated the forum chat (at the bottom of the page).
If you are available right now we could chat while you test...

(I'm curentliy kind of occupied, but try to test)

Interesting.. With the DS1307 it does work, but not with my simufile...
I have two 328 and two WS2812 (and 2 logic analyzers on the data line)...
It does not seem to depent on the WS2812 (the ws2812_test works) and not on the two CPUs (it's also not working, when I only use one AVR)..
I have to try whether i used the old AVR MCU version

What is the logic analizer trigger?
Try using trigger none (if you are not using condition).

EDIT: what about only 1 LA?
EDIT2: 2 LAs work for me.

EDIT3:

I have to try whether i used the old AVR MCU version

I should not mind: old AVR should be converted to new ones.
But it could be some issue opening files from older versions.

EDIT4:
The best thing would be if I could test your circuit.
If it is a private project that you can't share, only the .hex is enought.
If you can't share even the .hex even only the circuit file could help.

YEs, it seems to be dependent on the trigger:
- When the trigger is on CH1 (and the signal is on CH1), then the curves get cleared
- When no trigger is used (and the signal is on CH1), then the curves do not get cleared

Ok... at least you have a workaround to use it.

An option to trigger by channel is using "condition" with CH1R for example.

I will try to reproduce the issue and investigate it.