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 10818 - [MDI] Source editor loses focus when maximized/restored
Summary: [MDI] Source editor loses focus when maximized/restored
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: mslama
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-03-29 06:58 UTC by Jan Chalupa
Modified: 2008-12-22 09:52 UTC (History)
2 users (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 Jan Chalupa 2001-03-29 06:58:48 UTC 
Steps to reproduce:

1. Start IDE in the MDI mode.
2. Open a .java file in the source editor.
3. Make sure the source editor window is active and the cursor is visible.
4. Click on the Maximize button in the title bar.
5. The cursor disappears from the editor pane. Pressing any keys has no (?) effect.
6. Click in the pane, make sure the cursor is visible, click the Restore button
-> same problem.

Note that Minimize&Restore works fine.
Comment 1 David Simonek 2001-04-09 18:17:42 UTC 
Reassignign to Marek Slama. The problem probably is, that after maximalization
(or restore), only whole frame gets focus, not component itself. Marek, find out
who stole the focus (JComponent.grabFocus, SwingUtilities.findfocusowner...) and
eitjer remove focus stealing or restore component's focus on proper place (after
max/restore action).
Comment 2 mslama 2001-04-11 16:06:20 UTC 
Fixed in main trunk
Change in org.netbeans.core.windows.frames.DesktopPane in method moveToFront and
MinMaxListener.selectFrame commented call of requestFocus on frame
(InternalFrameTypeImpl). It caused focus loss of inner top component (editor in
this case).
Comment 3 mslama 2001-04-17 14:24:08 UTC 
Status changed according to guidelines
Comment 4 Jan Chalupa 2001-05-05 20:40:55 UTC 
Target milestone -> 3.3
Removing the OPEN_IN_3.2 keyword.
Comment 5 Marian Mirilovic 2002-04-29 17:36:44 UTC 
verified in [nb_dev](20020429)
Comment 6 Quality Engineering 2003-07-01 16:33:32 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.
Comment 7 Jiri Rechtacek 2007-04-18 13:32:08 UTC 
*** Issue 101016 has been marked as a duplicate of this issue. ***