[236] Quickfix window displayed without focus

Michal,

This is a known problem - some users seldom experience this behavior.
Unfortunately, we still have not discovered any reliable way to reproduce
the problem. We are investigating it.

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I had this problem too. If I remember correctly I even couldn't give
the window focus by clicking on it.

But I now have another problem: Alt+Enter doesn't work anymore. :(

Ciao,
Jens

Michal Levy wrote:

Hi
Sometimes happens that when i press Alt+Enter on line with 'bulb', quick
fix window is displayed but without focus - focus stays in editor
window. So when i press arrow keys or enter, instead of selecting right
fix and confirming it, i am actually editing text...
This behavior is unfortunately not reproducible. Only thing that helps
is restart of VS.NET. My coworker always use same R# build but never
encountered this problem - same version of VSNET (2005), same OS (XP Pro
sp2).....

thanx
Michal Levy

Jens Winter wrote:

I had this problem too. If I remember correctly I even couldn't give
the window focus by clicking on it.

But I now have another problem: Alt+Enter doesn't work anymore. :(

Same behavior here! This is something i forget to mention. After presing
Esc, quickfix window disappears and after that all underlining and bulbs
disappears too - this is something new in the last build...

What helps here is pressing Ctrl + Alt + O (Optimize using). This action
helps in many other "strange" situations - for example when R# thinks
some identifier is not defined even it is.....

Michal Levy

Ciao,
Jens

Michal Levy wrote:

>> Hi
>> Sometimes happens that when i press Alt+Enter on line with 'bulb',
>> quick fix window is displayed but without focus - focus stays in
>> editor window. So when i press arrow keys or enter, instead of
>> selecting right fix and confirming it, i am actually editing text...
>> This behavior is unfortunately not reproducible. Only thing that helps
>> is restart of VS.NET. My coworker always use same R# build but never
>> encountered this problem - same version of VSNET (2005), same OS (XP
>> Pro sp2).....
>>
>> thanx
>> Michal Levy

Have had similar too. Restarting VS05 brought it back again though.