Bug 277026 - Status text should appear if the caret is immediately right of the error text
Summary: Status text should appear if the caret is immediately right of the error text
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 277019 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-05-19 18:21 EDT by Kevin McGuire CLA
Modified: 2019-09-06 16:14 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin McGuire CLA 2009-05-19 18:21:24 EDT
When you have an error in say a java source editor, the status line in the bottom left of the window will show the error description text provided:

1) The text insert cursor is within the text run with the red underline squiggle
2) The text insert cursor is to the immediate left of the first character with the red underline squiggle

What I propose is that it'd be good to also fill the status line if:

3) The text insert cursor is to the immediate *right* of the *last* character with the red underline squiggle.

This is because it's common to type, then get the error squiggle on the thing you just typed.  By providing error text with this insert cursor location, you can see the error description in the status immediately on creation of the error, without say having to change cursor location, hover over the error, etc. 

In addition to this speeding up development, it'd also be a huge boon for accessibility, since a typing error (which can be likely for those with motor skill problems) can be immediately read off without any other mouse/keyboard use. Presumably it'd also be helpful for those using voice dictation.

Presumably we'd rely on the same delay on typing that we get presently (i.e. errors don't appear immediately, only once you pause your typing).  This would hopefully avoid getting annoying perky error text constantly changing in the status until you've finished typing what you intended.
Comment 1 Dani Megert CLA 2009-05-20 02:52:21 EDT
Could do this. However, this introduces a new corner case we need to handle somehow:

"this is an error"<caret>"this is an error too".

But that's a solvable problem.
Comment 2 Dani Megert CLA 2009-05-20 03:27:55 EDT
*** Bug 277019 has been marked as a duplicate of this bug. ***
Comment 3 Kevin McGuire CLA 2009-05-20 09:52:42 EDT
(In reply to comment #1)
> Could do this. However, this introduces a new corner case we need to handle
> somehow:
> 
> "this is an error"<caret>"this is an error too".

If there's no space between the two, isn't it a single error?

In any case, I admit that one concern I have with my suggestion is that the status line could become "noisy" for some. A slow typist can produce errors while they are still typing, which would cause not only the current {underline + red X + red square on right margin} feedback but now also status line flashing. That's a lot of (premature) feedback. For example, if I'm typing,

  String foo = "<caret>"

and I pause while typing between the quotes(say I'm trying to get the wording right), I get an error since no ';' and the error won't go away until I add the ';'.
Comment 4 Dani Megert CLA 2009-05-21 09:53:53 EDT
>If there's no space between the two, isn't it a single error?
It's not just errors that we show. You can e.g. also have something like this:
<warnStart>....<errorStart>....<errorEnd>.....</warnEnd>
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:14:55 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.