Intention lightbulb (only errors) disappears

Hi all,

I tried to do some searching on "intention" or "lightbulb" and "disappears" but couldn't find anything related, so forgive me if my searching is inadequate.

I've tried this under both 6.0.2 and the 6.0.3 beta (build 6140)

I'm having an issue with the intention lightbulb disappearing whenever my cursor no longer is hovering over an error. For example, if I type a reference to a class field that I've not yet created (this.newField) it hilights the field red. If I mouse over the red field name, I get the "error intention" bulb. Usually I can just move my pointer over the bulb, click the bulb and select the drop down option. However, as soon as my mouse pointer is no longer over the red field name, the bulb disappears, never allowing me to click it. This, of course, devolves into Pavlovian behavior where I try to move my mouse pointer fast enough to click the bulb before it disappears.

Is there some simple fix or something I need to change -- or is this an actual bug that needs to be reported?

Thanks.

4 comments
Comment actions Permalink

Hello Phil,

PB> I tried to do some searching on "intention" or "lightbulb" and
PB> "disappears" but couldn't find anything related, so forgive me if my
PB> searching is inadequate.
PB>
PB> I've tried this under both 6.0.2 and the 6.0.3 beta (build 6140)
PB>
PB> I'm having an issue with the intention lightbulb disappearing
PB> whenever my cursor no longer is hovering over an error. For
PB> example, if I type a reference to a class field that I've not yet
PB> created (this.newField) it hilights the field red. If I mouse over
PB> the red field name, I get the "error intention" bulb. Usually I can
PB> just move my pointer over the bulb, click the bulb and select the
PB> drop down option. However, as soon as my mouse pointer is no longer
PB> over the red field name, the bulb disappears, never allowing me to
PB> click it. This, of course, devolves into Pavlovian behavior where I
PB> try to move my mouse pointer fast enough to click the bulb before it
PB> disappears.
PB>
PB> Is there some simple fix or something I need to change -- or is this
PB> an actual bug that needs to be reported?

Have you tried pressing Alt+Enter?

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Thanks Dmitry for the very fast response.

Alt-Enter does work -- thanks, that works for me in the mean time.

I do know that I could mouse to the lightbulb and click it in 5.1 and in fact, the standard intention bulb (yellow) does allow this behavior (such as "inline variable") in 6.0.

Should I enter a bug report for the error intention lightbulb?

0
Comment actions Permalink

It appears in one of the latest 6.0.x builds that I can now click on the lighbulb again, but ALT-ENTER works as a substitute as well. Thanks!

0
Comment actions Permalink

Hello Phil,

There is an issue about similar effect: http://www.jetbrains.net/jira/browse/IDEA-12013.
It appears in IDEA 6.0.* when user has a plugin which adds some specific
actions to main toolbar. Maybe this may help to find a workaround, if still
necessary.

Hi all,

I tried to do some searching on "intention" or "lightbulb" and
"disappears" but couldn't find anything related, so forgive me if my
searching is inadequate.

I've tried this under both 6.0.2 and the 6.0.3 beta (build 6140)

I'm having an issue with the intention lightbulb disappearing whenever
my cursor no longer is hovering over an error. For example, if I type
a reference to a class field that I've not yet created (this.newField)
it hilights the field red. If I mouse over the red field name, I get
the "error intention" bulb. Usually I can just move my pointer over
the bulb, click the bulb and select the drop down option. However, as
soon as my mouse pointer is no longer over the red field name, the
bulb disappears, never allowing me to click it. This, of course,
devolves into Pavlovian behavior where I try to move my mouse pointer
fast enough to click the bulb before it disappears.

Is there some simple fix or something I need to change -- or is this
an actual bug that needs to be reported?

Thanks.

Alexander.


0

Please sign in to leave a comment.