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 21082 - Properties are not shown when selecting node immediately after Editor is closed
Summary: Properties are not shown when selecting node immediately after Editor is closed
Status: VERIFIED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on: 11149
Blocks:
  Show dependency tree
 
Reported: 2002-03-01 15:10 UTC by David Kaspar
Modified: 2008-12-23 09:08 UTC (History)
3 users (show)

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 David Kaspar 2002-03-01 15:10:54 UTC
Properties are not shown when selecting node immediately after Editor is closed.

How to reproduce:

1) Set MDI window mode.2) Open Explorer, Properties Window.
3) Open Editor by Open action on some Java file.
4) Close Editor.
5) Note - No properties are shown in the Properties Window.6) Select some package.
7) ERROR - No properties are shown in the Properties Window.
8) Select some another node in the Explorer.
9) Note - Properties are shown.
Comment 1 Jiri Rechtacek 2002-03-07 20:20:50 UTC
[Mar 06 dev] In SDI ok; appears in MDI.
Hint: top component ExplorerPanel is activated later then node is
selected (and property changes fires). There are in
DefaultContainerImpl  call reactivateWithDelay() which delayed a top
component activation. In NbNodeOperation
TopComponent.getRegistry().getActivatedNodes() returns  a empty array
because activatedTopCompoment of RegistryImpl is null being.
activatedTopCompoment is set by reactivateWithDelay() in a next thread.
Looks a little complicated :(
Comment 2 _ ttran 2002-07-04 21:32:18 UTC
IMO ExplorerView should force update of global property sheet when it
gets focus.  The question is if it always gets focus even though the
user has that impression.  Often times the parent of the Explorer gets
the focus and does not pass it down.
Comment 3 Marek Grummich 2002-07-22 08:45:48 UTC
Target milestone was changed from '3.4' to TBD.
Comment 4 Marek Grummich 2002-07-22 08:51:21 UTC
Target milestone was changed from '3.4' to TBD.
Comment 5 Marek Grummich 2002-07-22 08:55:10 UTC
Target milestone was changed from '3.4' to TBD.
Comment 6 Marek Grummich 2002-07-22 09:25:16 UTC
Target milestone was changed from '3.4' to TBD.
Comment 7 Marian Mirilovic 2003-01-09 15:20:05 UTC
I am sorry, but it works for me in [nb_dev](20030109) /
[jdk1.4.2](b12)
Comment 8 Lukas Hasik 2003-07-16 15:53:13 UTC
verified