When I change the Mode of a NCrunch Tool Windows (mostly needed for NCrunch Tests) to Window (for Alt Tabbing it).
Then I cannot type in the Editor any more. Any Keystroke seems to be eaten by the Tool Windows.
Also, if the Tool Window is in float mode, and i click to Options Dot of that Window, then the Menu does not appear.\
Furthermore, if the Tool Window is in Window Mode, I'm unable to show the Rider Menu (New UI) when clicking on the Rider Main Hamburger Menu.
Thanks for reporting this, due to the technique we use to embed our toolwindows this was a problematic area during development. It seems we've missed the keyboard workflow here in certain use cases. I'm putting this on the board and we'll try and get this sorted. And can't give an ETA on it, it's a complicated interaction between our two processes.
We've released version 5.7, this has a lot of fixes for Rider. It's still in the review process for acceptance to the market place. In the mean time the manual zip install for Rider can get you access to it a bit faster.
The release notes are here: https://www.ncrunch.net/download/showChangeLog?version=5.7
The download is located here: https://www.ncrunch.net/download
I've improved the toolwindows specifically for the issues you reported. However, the menu was always accessible for me. The Windowed mode and the Options Dot are fixed. So I hope that the menu is fixed as well, if it isn't please let me know.
Thanks again for taking the time to report the issues.
This problem still occurs in 5.16.0.2 (editor windows doesn't respond to input). It starts responding again if switching to another app and then back to Rider, but as soon as the NCrunch Tests window is touched it repeats. Seems to only occur with Window View Mode.
JetBrains Rider 2025.1.3
Build #RD-251.26094.147, built on June 11, 2025
Had this yesterday again (and a couple of times last Week). But with a docked NCrunch Test Window (5.16.0.2).
I could reproduce it when NCrunch had detected build errors for a project, and I clicked in the NCrunch Tool Window on the Line with the Error, and was unable to type anything in that opened Document,
But I could type in other already open document windows
When I closed that Document Windows, and reopened without the help of NCrunch (Navigate To **Next Error**)
Then I could type and fix the error.
Sadly (or not?), after a Rider restart this happened not again.
As NCrunch is faster on detecting Syntax Errors then Rider itself, in this time and age. I use this workflow often on Refactoring which break the code.
Der-Albert.com wrote:
I could reproduce it when NCrunch had detected build errors for a project, and I clicked in the NCrunch Tool Window on the Line with the Error, and was unable to type anything in that opened Document,
But I could type in other already open document windows
Please let me know if you can find a consistent way to reproduce this. I appreciate it's certain to be extremely annoying.