Unnecessary name qualification of types sometimes

This just started happening to me in 5.1.1716.7. I was typing this:

shot1.png

Yet when I hit "." I get this expanded out:

shot2.png

My file has a using System.Windows at the top of it.

Note that this is inside of a ListBox-derived class. I'm guessing the fact that it has a property named "Visibility" is confusing it. Also, if I undo the above change and type "." again I get a different version that is the members of the local Visibility property, which is also something I don't want.

The Intellisense behavior built into VS2010 has the best behavior. It (a) does not ever expand out to System.Windows.Visibility and (b) handles the ambiguity by combining both the local enum property and the global type into a single listbox.

2 comments
Comment actions Permalink

Hello Scott,

This is a known problem and it's already reported here: http://youtrack.jetbrains.net/issue/RSRP-151446.
You're welcome to vote for this issue.
As to the different behavior when you undo the change and press . again,
a different kind of code completion kicks-in this time which shows different
results. We'll try addressing this problem as well in one of the future releases.

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

This just started happening to me in 5.1.1716.7. I was typing this:

Image:shot1.png

Yet when I hit "." I get this expanded out:

Image:shot2.png

My file has a using System.Windows at the top of it.

Note that this is inside of a ListBox-derived class. I'm guessing the
fact that it has a property named "Visibility" is confusing it. Also,
if I undo the above change and type "." again I get a different
version that is the members of the local Visibility property, which is
also something I don't want.

The Intellisense behavior built into VS2010 has the best behavior. It
(a) does not ever expand out to System.Windows.Visibility and (b)
handles the ambiguity by combining both the local enum property and
the global type into a single listbox.

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



0

Please sign in to leave a comment.