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 19292 - [40cat] Upon encountering breakpoint, move NetBeans to front
Summary: [40cat] Upon encountering breakpoint, move NetBeans to front
Status: CLOSED DUPLICATE of bug 47825
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P4 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: RANDOM
: 49628 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-01-10 17:39 UTC by Dustin Callaway
Modified: 2010-04-29 09:09 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dustin Callaway 2002-01-10 17:39:55 UTC 
It would be nice if whenever a breakpoint is encountered, the NetBeans IDE 
would receive focus and move to the front of all windows. Sometimes when 
testing a Web application it is difficult to when a breakpoint has been hit (as 
the browser sits and tries to load the response). JBuilder figured out a way to 
do this (whenever a breakpoint is encountered, it jumps to the front).
Comment 1 Jan Jancura 2002-01-15 15:57:19 UTC 
fixed in main trunk
Comment 2 Dustin Callaway 2002-01-16 17:53:33 UTC 
Thanks Jan! Great fix. Works in trunk code.
Comment 3 lleland 2004-08-25 12:18:46 UTC 
This issue has been re-opened and changed to a defect for the NetCat40
process.

NetBeans no longer gains the focus and moves in front of all windows
when a breakpoint is encountered during debugging.
Comment 4 Jan Jancura 2004-09-28 20:48:43 UTC 
*** Issue 49628 has been marked as a duplicate of this issue. ***
Comment 5 Jan Jancura 2004-10-29 08:45:36 UTC 

*** This issue has been marked as a duplicate of 47825 ***
Comment 6 Quality Engineering 2010-04-29 09:09:18 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.