Hi, thanks for sharing these issues. I'll try to address them individually.



The Tests Window is mounted into Rider using a system called Wormhole, which is a JB component they are using internally for ReSharper. It work basically by streaming UI functions through a shared memory pipe, and is still under development.

Unfortunately the actual mounting of the window into the IDE and the tech that pulls it through the pipe is not under NCrunch control. This means that we don't have a way to solve issues related to the snapping of tool windows. It's my hope that issues like this will be solved by JB over time as they continue to work on Wormhole.



Are these issues related to the snapping of the window? I haven't seen them before and I'm wondering if you have a consistent way to reproduce them. There might be more I can do about them.



Right now RDI under Rider suffers from a range of issues that are interfering with the engine being able to pipe data into the UI. The good news is that I'm suffering with these problems too, and I've been working to fix them as I discover them. I have a number of fixes for this already pending in v5.16 and will push them when I've had a bit more time to test them myself.

RDI support was the last feature added to Rider in the 3-4 year development cycle, so it makes sense that it will have the most issues, since we had less time to dogfood and stabilise this area. Because it's also relying on piping the whole UI through shared memory, it's never going to be as responsive as what we have in VS ... but it IS supposed to work.



NCrunch's VS package has the benefit of 16 years of development, testing, Q&A, dogfooding, and all of that. We've only had support for Rider for a little over a year, and it's still in beta. Rider is much more challenging to support because the native IDE is JVM based, so we don't have an easy way to share code between the engine and the IDE.

I don't expect that it will be possible to get Rider's plugin as fast or as reliable as the VS one, but we're more or less at parity in terms of features... now it's just getting the stability worked out.

I've had a go at reproducing this on my own machine (I use NVIDIA Surround too), but it doesn't seem to happen on my end. Probably there is an environment component to the problem. You've mentioned that this seems to affect other non-NCrunch tool windows in Rider too? Do the effects seem to be similar?

If you resize the tool window, or close and reopen it, does it fix the problem? In theory this should trigger a refresh.

Unfortunately rendering our tool window in the same manner as a code window isn't an available option, as this won't enable the wormhole functionality we need to pipe the UI between processes.

My options in solving these issues are quite limited. My best hope is that if I can identify when the issues appear, I can force the system to just do a full refresh of the window to try and clear it.