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 7594 - Form is not repainted after deleting some component from it.
Summary: Form is not repainted after deleting some component from it.
Status: CLOSED WONTFIX
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P4 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-09-07 09:41 UTC by Jan Stola
Modified: 2003-06-30 18:27 UTC (History)
0 users

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 Stola 2000-09-07 09:41:46 UTC 
Build 1093 and 23
-----------------
Steps to reproduce:
1. Open some of the following forms: AWT Panel, AWT Applet, AWT Dialog.
2. Add some Swing component into it.
3. Delete this component.
4. The form editor window will not be repainted. The component still will
   be shown in the form editor window. It disapears only if you force
   repainting by hiding it by another window.

* The deleted component must be Swing component-for AWT component it works fine.
* The funny thing is that the deletion works for AWT Frame.
* If you put some container to the form, put the Swing component into it
  and then try to delete this component from the container than the deletion
  works fine. So if you want to reproduce this bug you should put the swing
  component right to the newly created form.
Comment 1 Tomas Pavek 2000-09-07 14:17:59 UTC 
This is caused by mixing AWT and Swing components and containers.
Form editor uses internally a Panel as top container for Dialog, Applet and
Panel design forms. This AWT Panel is not correctly repainted if it contains
Swing components and has a Swing layout. I suppose this could be fixed by using
JPanel instead (during design). But I'm not sure if this won't affect AWT
components then...
However, user can still put a Panel with Swing components into the form
manually and the problem is back... I think Swing components should not be put
into AWT containers. (Does it make sense to warn the user not to do it?) Even
if we got round this problem at design time it wouldn't work at runtime.
So I suggest to keep the current implementation.
Comment 2 Marian Mirilovic 2000-11-13 14:42:59 UTC 
*** Bug 8375 has been marked as a duplicate of this bug. ***
Comment 3 Quality Engineering 2003-06-30 18:27:37 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.