Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Color scheme reverts to default, but configuration still shows the correct colors. VS 2012
AntonioDrusin100
#1 Posted : Monday, November 19, 2012 4:16:54 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 11/9/2012(UTC)
Posts: 2
Location: United States of America

Thanks: 1 times
Was thanked: 1 time(s) in 1 post(s)
I changed the color scheme of the tool windows to match VS 2012, and it worked correctly for a week or so. Starting today, the colors always revert to standard for the Tests and Coverage tool windows. The configuration tool windows displays the correct settings and interestingly has also the correct colors. If I change the colors in the configuration just a bit, the tool windows then pick up the correct color change.

Every time I quit and restart VS 2012, the Tests and Coverage windows revert back to default colors again and the Configuration window has the correct colors in the settings and is also displaying with the correct colors.

This is only a minor annoyance as I have one bright screen with the NCRUNCH data and the rest is dark. Anyone with the same problem?
Remco
#2 Posted : Monday, November 19, 2012 7:55:16 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,123

Thanks: 957 times
Was thanked: 1286 time(s) in 1193 post(s)
Hi, thanks for posting!

The colour control for the tool windows is still a new feature, so it's quite possible there is a problem here. Do the windows adjust to their correct colouring when NCrunch is first enabled? NCrunch doesn't actually identify any tool windows until it is first switched on - so this is when the colour configuration should be applied.


Cheers,

Remco
1 user thanked Remco for this useful post.
AntonioDrusin100 on 11/19/2012(UTC)
AntonioDrusin100
#3 Posted : Monday, November 19, 2012 10:24:57 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 11/9/2012(UTC)
Posts: 2
Location: United States of America

Thanks: 1 times
Was thanked: 1 time(s) in 1 post(s)
Thank you for your very quick response. It turns out it's a "user" error. I cleaned my source code folders and that disabled NCrunch for the project. I did not have to run tests until just now. Enabling NCrunch fixes the issue instantly. I'd say not a bug.
1 user thanked AntonioDrusin100 for this useful post.
Remco on 11/19/2012(UTC)
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.036 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download