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 153808 - [65cat] IDE doens't remove node for component if the bean is no more a container
Summary: [65cat] IDE doens't remove node for component if the bean is no more a container
Status: NEW
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@guibuilder
Depends on:
Reported: 2008-11-24 20:52 UTC by Michel Graciano
Modified: 2008-11-25 11:03 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Michel Graciano 2008-11-24 20:52:47 UTC
[ BUILD # : 6.5 ]
[ JDK VERSION : 1.6.0_07 ]

If I change a component as a container for a while, for example, if
the component there is bean info it is the default behaviour, and if
I create a bean info correctly, the already created GUI are not
updated when I open it on the visual editor. IMO, it should ask user
about change it, that the component XYZ is no more a container and
the node and nested components will be removed, just in case it has
some component inside, if not, just remove the node.
When I talk node, I am talking about Inspector view. BTW, if I remove
the component and reinsert everything works, but I prefer for now
update my forms by hand, which is a high risk operation.
Comment 1 Jiri Vagner 2008-11-25 09:18:12 UTC
Thank you for your report. While custom component is changing from container type to non-container type, IDE should
throw dialog and warn user of inner components loss. Did I understand your enhancement correctly?
Comment 2 Michel Graciano 2008-11-25 11:03:07 UTC
Yes, that is it. Probably, the correct approach is ask to user about it, if he wish proceed with the fix (remove the
nested components) or open as read only, so user has a chance to understand what is going on and maybe copy components
to another form and so on. BTW, the cases where I can see it is when we use a component without bean info (as
JXMonthView from SwingX) and when we fix it for our projects and form already exists, the IDE show a error on log files
that layout could not be found, but the layout is just necessary for containers... so it is not the error, the problem
is that the component should be define as a non container. I hope to be clear about my points.
BTW, 6.5 are working really well with third-party components. :)