Build 89 feedback/bugs

1. If I am editing to the right of the edit screen, any R# intellisense windows try to not stomp off the right of the edit screen (I.E. the intellisense window seems to be right-bounded within the edit window). This often means that the intellisense window can be so narrow that I can't actually see any text in it.

2. If I do a rename variable on a local variable and R# presents an in-place edit, pressing CTRLV to paste the new name in causes R# to crash. This often happes when I do the following: type new variable name, remember I have R#, CTRLW, CTRLC, CTRLZ, SHIFT-F6, CTRL+V R#CRASH

3. (From 2) I would love to send the crash report to you, but this feature STILL DOES NOT WORK through a proxy (even if I set the proxy to match my IE settings).

4. I am getting (and have had for many R# versions) a rogue window on my secondary monitor. This is almost certainly introduced by R#. The window does not seem to affect the IDE, but I do notice that when R#/VS.NET decides to get really busy (and 'hangs' the IDE for a while), then this secondary window can take up the entire second monitor, and the main IDE window goes completely white. Both the main window and the rogues window cotnain the VS.NET title bar. It is all quite strange. I also noticed that if I try to close this rogue window by clicking the close X, that causes the main VS.NET IDE close X icon to depress and prompts me to shut down VS.NET. As I said, quite strange behaviour.

That said, I still can't stop using R#. Its great.

3 comments
Comment actions Permalink

1. If I am editing to the right of the edit screen, any R#
intellisense windows try to not stomp off the right of the edit screen
(I.E. the intellisense window seems to be right-bounded within the
edit window). This often means that the intellisense window can be so
narrow that I can't actually see any text in it.


Try it in the build #90. It seems to be fixed there.


2. If I do a rename variable on a local variable and R# presents an
in-place edit, pressing CTRL+V to paste the new name in causes R# to
crash. This often happes when I do the following: type new variable
name, remember I have R#, CTRLW, CTRLC, CTRLZ, SHIFT-F6, CTRLV
R#CRASH


I could not reproduce this. Could you please send submit the exception stacktrace into the Tracker and write steps to reproduce into the request?


3. (From 2) I would love to send the crash report to you, but this
feature STILL DOES NOT WORK through a proxy (even if I set the proxy
to match my IE settings).


We'll try to investigate it.


4. I am getting (and have had for many R# versions) a rogue window on
my secondary monitor. This is almost certainly introduced by R#. The
window does not seem to affect the IDE, but I do notice that when
R#/VS.NET decides to get really busy (and 'hangs' the IDE for a
while), then this secondary window can take up the entire second
monitor, and the main IDE window goes completely white. Both the main
window and the rogues window cotnain the VS.NET title bar. It is all
quite strange. I also noticed that if I try to close this rogue window
by clicking the close X, that causes the main VS.NET IDE close X icon
to depress and prompts me to shut down VS.NET. As I said, quite
strange behaviour.


We have absolutely no idea what it can be. Could you send us a screenshot?


That said, I still can't stop using R#. Its great.


Thank you :-)!

--
Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com "Develop with pleasure!"


0
Comment actions Permalink

1. R# intellisense window. Have not checked yet

2. Paste with an inline Rename works fine in build 90

4. Rogue window appears to have vanished in build 90

0
Comment actions Permalink

James Hebben wrote:

1. If I am editing to the right of the edit screen, any R# intellisense windows try to not stomp off the right of the edit screen (I.E. the intellisense window seems to be right-bounded within the edit window). This often means that the intellisense window can be so narrow that I can't actually see any text in it.

2. If I do a rename variable on a local variable and R# presents an in-place edit, pressing CTRLV to paste the new name in causes R# to crash. This often happes when I do the following: type new variable name, remember I have R#, CTRLW, CTRLC, CTRLZ, SHIFT-F6, CTRL+V R#CRASH

3. (From 2) I would love to send the crash report to you, but this feature STILL DOES NOT WORK through a proxy (even if I set the proxy to match my IE settings).

4. I am getting (and have had for many R# versions) a rogue window on my secondary monitor. This is almost certainly introduced by R#. The window does not seem to affect the IDE, but I do notice that when R#/VS.NET decides to get really busy (and 'hangs' the IDE for a while), then this secondary window can take up the entire second monitor, and the main IDE window goes completely white. Both the main window and the rogues window cotnain the VS.NET title bar. It is all quite strange. I also noticed that if I try to close this rogue window by clicking the close X, that causes the main VS.NET IDE close X icon to depress and prompts me to shut down VS.NET. As I said, quite strange behaviour.

That said, I still can't stop using R#. Its great.


IIRC this secondary window as described in 4) has nothing to do with
Resharper. It's used by VS.NET as a temporary container for controls
when using a designer.

Regards,
Thomas

0

Please sign in to leave a comment.