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 17313 - Clicking on an error doesn't necessarily show the source
Summary: Clicking on an error doesn't necessarily show the source
Status: CLOSED DUPLICATE of bug 17320
Alias: None
Product: cnd
Classification: Unclassified
Component: Terminalemulator (show other bugs)
Version: 3.x
Hardware: PC Windows 95/98
: P3 blocker (vote)
Assignee: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-06 00:54 UTC by David-john Burrowes
Modified: 2008-12-23 08:11 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David-john Burrowes 2001-11-06 00:54:25 UTC
If a source file which contains an error is already open, then single clicking on an error in the output window will display the offending line in that source 
file.
However, if it isn't open, single clicking on the error in the output window does nothing.  It takes a double click to open the source file and show the 
offending line.

Given that hyperlinks are being used here, I would certainly expect a single click to open the file.
Comment 1 akemr 2001-11-19 10:40:23 UTC
As designed. Single click has other behaviour as double click.
Comment 2 David-john Burrowes 2001-11-19 19:19:31 UTC
Sorry, I've got to reopen this, though I've marked it for 3.4 since I assume it is too late to fix 
this for 3.3.

This may be as designed, but it is a bad design (maybe it should be marked as an enhancement?).  It 
is bad because in all other contexts, it takes a single click to activate a hyperlink.  What is most 
likely to happen is that new users will click once on them, nothing will happen, and they'll assume 
they're broken.  If they discover double click works (as I did) they'll still probably find it hard 
to adjust since hyperlinks (even elsewhere in the IDE) generally take a single click to be 
activated.

I guess my point is: if these things are going to look like hyperlinks, they should behave like 
hyperlinks (single click).  Either make them behave normally or don't make them look like 
hyperlinks.

If there is a conflict with a single click doing something else (what does it do?), then either that 
should change or these shouldn't look like hyperlinks.
Comment 3 akemr 2001-11-20 08:37:48 UTC
OK, I agree this shouuld be solved. I'm marking it as DUPLICATE of
#17320 to be solved together (if you have no objections)

*** This issue has been marked as a duplicate of 17320 ***
Comment 4 David-john Burrowes 2001-11-21 19:35:57 UTC
Yes.  I agreee.  I guess they are, indeed, closely related.
Comment 5 Quality Engineering 2003-07-01 15:56:54 UTC
Resolved for 3.4.x or earlier, no new info since then -> verified.

Comment 6 Quality Engineering 2003-07-01 16:32:06 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.
Comment 7 Quality Engineering 2008-12-23 08:11:54 UTC
moving terminal emulator issues to terminalemulator component.
To see the correct version and target milestone of this issue look at Issue
Activity table.