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 94745 - RFE: Reopening a page collapses Page1 node, by default it should expand to show form1 contents
Summary: RFE: Reopening a page collapses Page1 node, by default it should expand to sh...
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Peter Zavadsky
Depends on:
Reported: 2007-02-06 20:07 UTC by bugbridge
Modified: 2007-02-06 20:07 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2007-02-06 20:07:10 UTC
Original status: 3-Accepted; Suggested Status: NEW

Original submitter: sakthivelg

shortfin build 060927_9 on Xp

+ create new project 
+ drop a few components and see now that outline shows the form1 node expanded
to show off all the components
+ close and reopen page/project, the page1 node is collapsed
* user needs to expand a few levels down to see the components underneath the
form1 node.

This is not a regression. The fact that you see it expanded as before when you
closed the page and reopened, was the fact, that in leopard the nodes were not
garbaged which was an performance issue, this is fixed now.

You can see it, if in leopard close entire project, (then to be sure invokde
couple of time GC in the memory toolbar), and then reopen the project, you'll
see that the outline is not expanded either.
Please close as "not a defect" or make a RFE from this. And please remove the
regression keyword, the ability to remember the expansion wasn't in the old
outline either, it was working only due to the memory leak.

Evaluation (Entry 2):
OK. Changed it to RFE.
Removed REGRESSION keyword.

Evaluation (Entry 3):
Thanks, this would need to impl also remembering the expansion in the outline.
It depends how well the NB api allows that, and how well it could be applied to
always changing the design bean node structure (almost any change produces new
tree instances).