Don't merge this PR, this is a workaround and not a fix.
Tomorrow i'll do some test.

This is the commit that introduced .DoEvents():
ff0f219 winforms control improve mouse responsiveness

This rabbit hole is pretty deep, this is where i'm at.

• I'm testing with 10.000.000 points, not 100
• Removed all .DoEvents()
• skipIfCurrentlyRendering shouldn't be needed anymore (globally, not only for the tracker demo)
• No more occasional white flickers
• There is a very small loss of perf (fluidity) that i still need to investigate

I hope it helps.

this is where i'm at

Here's the diff: main...AbeniMatteo:ScottPlot:ab-fix-doevents

• Removed all .DoEvents()
• skipIfCurrentlyRendering shouldn't be needed anymore

These are big wins! Using Control.Refresh() instead of Application.DoEvents() with Control.Invalidate() would be a great improvement if it's that easy.

This rabbit hole is pretty deep

This simple topic tends to explode in complexity every time I look into it... Thanks for your effort on this front! I look forward to seeing what you come up with

This is a small (in terms of lines) but pretty invasive change so i'll leave it up to you.

No changes since my last post, the stutter in both is caused by GC collections (flickers are only present now because of .Invalidate()).
I tested all the demos and didn't notice any problem.

Now:

After:

Thanks for your work on this @AbeniMatteo!

I copied your changes from main...AbeniMatteo:ScottPlot:ab-fix-doevents into this PR and am merging it now.

I think you left .Invalidate() in.

Is there a sure enough way to eliminate the stack overflow exception during Refresh() calls?

As far as I've tried, this issue is still present.

Is there anything I can do to reduce the refresh frequency with the default interactions?