Various ReSharper 6.1 Usability Issues

Hi,

I downloaded R6. Looks great so far. Congrats! However, I have some issues:

UPDATE: STILL AN ISSUE WITH 6.1.

1 - Stop CTRL fade


Is there any possible way to kill the "fade" that occurs when you press and hold the CTRL button in Resharper?

I use CTRL+P (emacs emulation Up Arrow) and CTRL+N (emacs emulation Down Arrow) when selecting items from a menu such as "Navigate > Go To File" mini popup. When I press CTRL+N to move my selection down, the "Go To File" menu fades.

It would be great there was any possible way to kill the CTRL fade that goes on in R#.

If not, perhaps I could write a R# plugin that will kill this CTRL fade - just give me a general idea where to look in Resharper's Open API.

I use an OS wide emacs emulation:
http://www.cam.hi-ho.ne.jp/oishi/indexen.html

2 - Color Highlighting Issue with Intellisense


http://www.bitarmory.com/temp/rcolor.png
* ReSharper - Options: IntelliSense > General:
    Use IntelliSense features of: Resharper checked
    Completion Appearance: Visual Studio IntelliSense font

* My Windows 7 Theme Settings:
    Control Panel > Appearance and Personalization > Personalization: Windows Classic Theme

* Using Visual Studio 2010 RTM

Notice the blue selected item hightlight and blue text color match highlight. This is very hard to see. How do I fix this?

Many Thanks,
Brian

8 comments

the ctrl fade seems to be feature by visual studio, not resharper
some option to disable it would be fine, perhaps there does exist some stand alone extension doing this?

visual assist seems to have an option for this
http://stackoverflow.com/questions/4721551/vs2010-intellisense-would-fade-if-press-ctrl-key

0

Hi Sven,

Yea, Visual Studio does implement CTRL fade; however, ReSharper does not "inherit" this fade behavior from Visual Studio for ReSharper's windowing.

ReSharper, by convention, follows the same CTRL key experience - but the actual fade implementation of ReSharper windows & dialogs belongs to ReSharper itself.

I think ReSharper is catching the CTRL key and fading whatever R# window/dialog is active - somewhere... :|

0

I get your point. I guess this question can answer only a developer.

0

Made progress on ISSUE #1... killed the transparency using a ShellComponent:



[ShellComponent(Sharing.Product, Lifecycle.Container, Creation.PrimaryThread, Access.PrimaryThread)]
public sealed class KillTransparencyFadeFeature
{
public KillTransparencyFadeFeature()
{
     var field = typeof(GoTransparentOnControlKey)
                 .GetField( "OpacityFactorWhenTransparent",
                               BindingFlags.NonPublic |
                               BindingFlags.Static );
     try
     {
        field.SetValue( null, 1.0 );
     }
     catch{}
}
}


It's a hack... but WORKS. Thank goodness. It was driving me nuts.


Now, just need some insight/help on hacking the ISSUE #2.... Fixing the SystemColor.Highlight blue colors in IntelliSense.

Thanks,
Brian

0

I guess changing the highlight color is no option for you.
have you tried so look for an entry in the fonts and colors list for the "blue" used in intellisense?

0

Finally!



PLEASE fix this problem future versions. At the very least, allow us pick the color of the MatchResult highlighter!

I had to hack-the-hell-out of Resharper 6 to get my intellisense highlighting to work right.

PLEASE DO NOT HARD CODE THE COLOR BLUE in

JetBrains.ReSharper.Feature.Services.Lookup.
          MatchingResult.HighlightMatchingSymbols()


  text.SetForeColor(Color.Blue, num 1)

... THIS CONFLICTS WITH MY KnowColor.Highlight and SytemBrush.Highlight !

http://www.bitarmory.com/temp/rcolor.pnghttp://www.bitarmory.com/temp/rcolor2.png

0

Submitted an Issue on the tracker. Hopefully, this will get some attention:

http://youtrack.jetbrains.net/issue/RSRP-273580

Thanks,
Brian

0

*BUMP*

Can someone please give this issue some attention? I'd hope this highlight bug would get fixed in the next 6.1.1 release....

http://youtrack.jetbrains.net/issue/RSRP-273580

Thanks,
Brian

0

Please sign in to leave a comment.