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 34908

Summary:	core/output: don't disable NextOutJumpAction in constructor
Product:	cnd	Reporter:	Torbjorn Norbye <tor>
Component:	Terminalemulator	Assignee:	_ tboudreau <tboudreau>
Status:	VERIFIED FIXED
Severity:	blocker
Priority:	P3
Version:	3.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:
Bug Depends on:	28297, 30536
Bug Blocks:	34894

Description Torbjorn Norbye 2003-07-13 04:18:54 UTC

See issue 34894 (part #1).

The output window, as part of its
-initialization-, disables the "Next Error"
action. There's no need to do it this early (the
Output Window's initialization happens on startup
even when there is no Output Window open; see
stacktrace listed in issue 34894). 

The Next Error action is already disabled from
startup. So, the Output Window only needs to
update its state whenever the Output Window is
opened (or cleared/compilation restarted).

The reason for this is that some other windows,
such as the suggestions view, also hooks into the
Next/Previous buttons. If these windows are made
visible at startup, one of them should get to own
the F12 key, but now the output window which isn't
even visible goes and sets the action performer to
null which disables it.

Comment 1 Jesse Glick 2003-07-13 04:57:28 UTC

A proper solution to issue #30536 might solve this for free.

Comment 2 _ tboudreau 2003-11-27 17:15:22 UTC

Fixed as part of fix for 37258 - see OutputTabInner 1.5.  It will now
check if the action performer is its own, and only set it to null if
it is.  I *think* that won't cause problems elsewhere.

Comment 3 Marian Mirilovic 2005-07-15 07:49:34 UTC

closed

Comment 4 Quality Engineering 2008-12-23 08:34:51 UTC

moving terminal emulator issues to terminalemulator component.
To see the correct version and target milestone of this issue look at Issue
Activity table.