request tooltip for errors and warnings when using keyboard

Answered

Hi,

If you mouse over a piece of code hilighted in red (error) or yellow (warning), it immediately pops up a tooltip with the details about the error or warning.

I really like this feature, but I prefer using the keyboard, and I don't like having to reach for the mouse to see these tooltips.

If you put the caret inside a highlighted piece of code, the error/warning details show up in the status bar. However, I find this difficult to use because my eyes have to move from teh middle of the screen down to the bottom.

What I would prefer is to have the tooltip also popup for the caret after some configurable delay, e.g. 300 ms.

6 comments
Comment actions Permalink

Hi,
You can use Ctrl+F1.

TIA,
Dmitry

2
Comment actions Permalink

Thanks for the reply. I didn't know there was keybinding for that.

But I would still like to have the warning/error message autopopup. It is much more convenient then hitting a key.
Also, many new users will probably do the same thing I did switching to the mouse to show the tooltip, because it is not obvious that there is a keybinding to show that.

I think the need is more pressing for me because I am making heavy use of the Inspection Gadgets plugin to highlight possible problems as warnings (yellow). Sometimes I load a file in the project and the gutter is lit up solid yellow almost because there is so many warnings.

In those situations, I run Tools->Inspect Code on the file. The Inspection results window does a good job organizing the warnings, and makes it easy to apply the fix for all warnings of one type all at once.

The main annoyance with running Tools->Inspect Code, is that the settings for Inspect Code and the Error/Warnings dialgo are not shared; It is a pain to try to keep them in sync.
(See http://www.intellij.net/forums/thread.jsp?forum=15&thread=66112 )

0
Comment actions Permalink

-1 for both propositions. I don't want anything popping up if my mouse isn't over an element. Sometimes I spend a few minutes reading ahem legacy code, and a popup would distract me from that.

Also, the Error settings and the code inspections play different roles for me, and I can't see why their settings should be kept synced: usually my code inspect settings include a much broader set of options than my Errors options.

1
Comment actions Permalink

+ -1 for both propositions. I don't want anything popping up if my mouse isn't over an element. Sometimes I spend a few minutes reading ahem legacy code, and a popup would distract me from that.+

I think if it is like other popups, people who don't want it should be able to turn it off, i.e. autopopup error/warnings (ms) delay.

Also, the Error settings and the code inspections play different roles for me, and I can't see why their settings should be kept synced: usually my code inspect settings include a much broader set of options than my Errors options.

The main point was that the Errors/Warnings should use the same Named Profiles that Tools->Inspect Code uses. Then you could use either the same profile for both, or two different profiles. It is helpful in team environment to be able to share the warnings/errors settings like we can share the Code Styles.

0
Comment actions Permalink

Em Sat, 19 Jun 2004 08:11:11 +0400, Alex escreveu:

I think if it is like other popups, people who don't want it should be
able to turn it off, i.e. autopopup error/warnings (ms) delay.


Oh, NYAO.

The main point was that the Errors/Warnings should use the same Named
Profiles that Tools->Inspect Code uses. Then you could use either the
same profile for both, or two different profiles. It is helpful in team
environment to be able to share the warnings/errors settings like we can
share the Code Styles.


Ah, I see. If named profiles are implemented for the error settings
(there is an old request for this), +1 for sharing the profiles.

--
Marcus Brito <pazu@animegaiden.com.br>


0
Comment actions Permalink

Just in case anyone else sees this years later, the shortcut on Mac is Command+F1 (⌘+F1).

0

Please sign in to leave a comment.