Any time tool window disappears (autohide or any other tool window activates on the same VS dock side) tree with my tests collapses.
Version 1.46.0.20
VS: 11.0.60610.01 Ultimate
NET: 4.5.50709
very annoying
Daily Usage Issues
Tests tree in NChrunch Tests tool window collapses on tool window hide
Started by Yaro77 on 6,209 views
Remco NCrunch Developer
#4615
17 Sep 2013 11:16 UTC
Hi, thanks for sharing this issue.
Does this happen if the Tests Window is not docked with any of the edges in Visual Studio? (i.e. if its floating?)
There shouldn't normally be anything unique about this window. Sorry if this seems like a stupid question, but are you certain that the 'pin' on the window has been pushed down? The behaviour you're describing sounds like the normal VS design if the tool window is docked but not pinned.
Does this happen if the Tests Window is not docked with any of the edges in Visual Studio? (i.e. if its floating?)
There shouldn't normally be anything unique about this window. Sorry if this seems like a stupid question, but are you certain that the 'pin' on the window has been pushed down? The behaviour you're describing sounds like the normal VS design if the tool window is docked but not pinned.
Remco, we talking about the completely different things. I guess, it's my fault.
I made a video for you: Youtube
I made a video for you: Youtube
Edited 17 Sep 2013 21:06 UTC
Remco NCrunch Developer
#4618
17 Sep 2013 23:23 UTC
Thanks for the clip - this definitely shows the problem very clearly.
It looks as though VS is deconstructing the tool window and reinitialising it when it becomes visible. This resets the collapse status in the grid.
The upcoming V2 release is a complete rewrite of the code in this area, and I believe it should have solved this issue. There may be options to solve this in the V1 release .. I'll take a look. Thanks for reporting this issue.
It looks as though VS is deconstructing the tool window and reinitialising it when it becomes visible. This resets the collapse status in the grid.
The upcoming V2 release is a complete rewrite of the code in this area, and I believe it should have solved this issue. There may be options to solve this in the V1 release .. I'll take a look. Thanks for reporting this issue.
Post a reply
Log in to reply.