Quick-fix menu too slow

Hi,

When I'm typing, I'm usually quicker than the ReSharper Quick-fix menus, which is rather annoying. If I'm cleaning up a file and, say, making some fields read-only, I'll do that for each field. If I, after I'm done making the fields read-only, press page up to remove unused using statements, I press "alt+enter, enter", without looking at the quick-fix (it's always remove unused using statements), I often insert missing xml-documentation or something else, completely unrelated to the context of the position of the caret.

I hope to see some performance improvements in this area, before the release of R#6.


Kenneth

6 comments

Current builds often seem to have the wrong content in the quick-fix menu if you're working fast, I agree.   It looks like some kind of background processing is incomplete at the point the menu opens - open it a second time and it's ok.

Seems to me it would be better to block the popup rather than open it quickly but with the wrong content.

0

Hello Kenneth,

Thank you for reporting this problem! You can track the progress here: http://youtrack.jetbrains.net/issue/RSRP-269498.


Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hi,

When I'm typing, I'm usually quicker than the ReSharper Quick-fix
menus, which is rather annoying. If I'm cleaning up a file and, say,
making some fields read-only, I'll do that for each field. If I, after
I'm done making the fields read-only, press page up to remove unused
using statements, I press "alt+enter, enter", without looking at the
quick-fix (it's always remove unused using statements), I often insert
missing xml-documentation or something else, completely unrelated to
the context of the position of the caret.

I hope to see some performance improvements in this area, before the
release of R#6.

Kenneth

---
Original message URL:
http://devnet.jetbrains.net/message/5304847#5304847



0

I haven't gotten far enough along in ReSharper 6 to see how this works, but
in ReSharper 5 I could usually perform a series of quick fixes with
AltEnter, CtrlPgDn if I was quick on the keys. If my fingers stumbled, it
would either apply the wrong quick fix (because it would have something
undesirable in the top spot instead of say make readonly or rename to match
naming convention) or I would have to wait for the analyzer to complete
before something reasonable appears in the top spot of the quick fix menu.

"Kenneth Siewers Møller"  wrote in message
news:32306853.99921306822320301.JavaMail.devnet@confluence.jetbrains.net...

Hi,

When I'm typing, I'm usually quicker than the ReSharper Quick-fix menus,
which is rather annoying. If I'm cleaning up a file and, say, making some
fields read-only, I'll do that for each field. If I, after I'm done making
the fields read-only, press page up to remove unused using statements, I
press "alt+enter, enter", without looking at the quick-fix (it's always
remove unused using statements), I often insert missing xml-documentation or
something else, completely unrelated to the context of the position of the
caret.

I hope to see some performance improvements in this area, before the release
of R#6.


Kenneth

---
Original message URL: http://devnet.jetbrains.net/message/5304847#5304847

0

Hi,

Unfortunately I couldn't reproduce this behavior. Could you please send us your file (or any solution) for investigation? By the way, do you have additional plugins / addins installed in VS 2010 environment? Great thanks in advance!

Kirill Falk

0

Hi,

Sorry for the late reply.

The problem isn't related to any specific project or solution, it simply ReSharper that takes too long to change it's context. As I described, if I'm at one quick-fix and quickly moves to another and press alt+enter, the quick-fixes are incorrect and still applies to the previous position of the caret.
I have just recently begun to notice this, so I believe it's a problem introduced with the latest EAP.


Best regards,
Kenneth

0

Still present in 2159 (it just did it to me), though it might be less prevalent than in earlier builds.

0

Please sign in to leave a comment.