It looks like Azure dislike imports ordering in whole project. I think it's bad idea fix it in this PR.

It looks like Azure dislike imports ordering in whole project.

This is surprising! It looks like the command dotnet format now sorts using statements, but it previously did not do this 🤔

It looks like I fixed it: I ran dotnet format on the master branch (04e4f5c), then re-ran the Azure Pipelines job on this PR. All green! 👍

Note to self: setting up the auto-formatter is discussed in #425:

dotnet tool install --global dotnet-format
dotnet format

Application.DoEvents

I like your processEvents argument. I'm not happy with this system as a long-term solution, but this argument is an excellent immediate improvement! Thank you for this PR - it may have taken me a long time to figure this one out.

Resize() in MatchAxis()

The intended purpose of Resize() was to match the layout (padding and tick density), not just axis limits. A changed layout means new bitmaps, so this is necessary when the source layout changes. This is what it looks when you zoom out really far on the top graph:

However, the invention of an improved layout system #156 meant that TightenLayout() served this function (layout wasn't recalculated on every resize). The Render() you found was old, and has been changed to TightenLayout() (which also calls Render()) to properly resize the layout after the axis changes.

Big Picture

ScottPlot has evolved so much over the last year that its architecture drifted from what the original user controls had in mind when they were designed. This is a topic for another discussion, but my point is there is much room for improvement by refactoring how ScottPlot handles bitmaps (e.g., they should not be stored or resized, IDisposable objects should be better respected, and using separate Bitmaps for the frame vs. data is a bad idea). I plan to improve these things incrementally, but hopefully there will be more time when active issues/PRs slow down again.