This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 31017 - Editor window does not gain focus when clicking compiler errors
Summary: Editor window does not gain focus when clicking compiler errors
Status: RESOLVED DUPLICATE of bug 13355
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@editor
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-13 08:03 UTC by randahl
Modified: 2007-11-05 13:44 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description randahl 2003-02-13 08:03:01 UTC
When you click an error message in the compiler output 
window, NetBeans is supposed to find the relevant source 
file, show it in the source editor, and jump to the line 
where the compiler error is. This works, but on Windows XP 
the the editor does not gain focus so you cannot 
immediately see the cursor position, thus you do not know 
which line to look at to correct the error.

Two other persons on the nbuser list has confirmed that 
this problem occurs with 3.4.1 (and, as I recall, also 
earlier versions of NB) but only on Windows XP.

The workaround is simple (although annoying): After 
clicking the error link in the compiler output window you 
can click the scrollbar of the source editor which will 
make the source editor get the focus.

To the person who chooses to fix this bug: You are most 
welcome to contact me at randahl@rockit.dk for any further 
information related to this issue.
Comment 1 Martin Roskanin 2003-02-13 08:32:32 UTC
It seems it is the same problem as issue #13355, the focus has been
lost and the first component of the editor toobar has been focused. I
am duplicating this issue. If the problem is different, please reopen
the bug. Or please try the latest builds, this bug should be already
fixed (issue #28728).

*** This issue has been marked as a duplicate of 13355 ***