Intellisense popup remains active
Sometimes, even when you are typing in the next coding line, the intellisense popup window from the previous line remains active and you must press 'esc' to close it.
Is there any solution to this problem?
Please sign in to leave a comment.
Could you please provide more details, some screenshots, maybe a screencast? Can you reliably reproduce this? Do you invoke the popup explicitly or does it appear automatically?
Yes of course.Here it goes :
Is the previous statement finished, are all the parentheses closed, is semicolon present?
Can you reproduce it reliably? I've just tried and I can't.
Just imagine the previous screenshot with me typing something at the next line.After 10 characters what I type is hidden below the 'help balloon' and you can't see what you are typing.
Eventually the balloon goes away but the editor could detect that you are writing in a new line, so that the IDE should turn off the balloon.
You could add code that detects when the user changes line and make the
balloon disappear.
The code that removes the balloon when outside the sc is already there, it's just that it doesn't work for some reason. That's why I need some steps to reproduce.
I must say that I use mac os (mountain lion) with JDK7 as the default java language of the system.
Thanks. Could you please describe a series of actions (typing, caret movements, code completion, etc) and provide a code sample such that you get this bug applying these actions to this code?
I believe that the above picture is more than suffice.I am typing at the next line and after 10 or so
characters I can't see what I am typing because of the balloon.
The picture doesn't contain the actions that you performed before. It also doesn't contain the text to the very right of the previous line, which is important.
I've uploaded a video to show you what I mean :
Thank you very much! Now I can reproduce it. I've filed a YouTrack request http://youtrack.jetbrains.com/issue/IDEA-99274, you can watch it.
Great news.Thank you very much Peter for the great support over a great product.
I see the youtrack thread, and it is saying that it is an old bug that is already fixed.
How is this possible?
5 days is not that old. Thanks to your report it's fixed now and scheduled for 12.1 release. There was an older duplicate found after the fixing.
Geat news.I'll wait for the 12.1 release then.