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 167044 - Design mode doesn't use the latest changes in some beans
Summary: Design mode doesn't use the latest changes in some beans
Status: CLOSED WONTFIX
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-13 21:07 UTC by Marian Mirilovic
Modified: 2009-12-03 03:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
screenshot (115.12 KB, image/png)
2009-06-13 21:08 UTC, Marian Mirilovic
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2009-06-13 21:07:59 UTC
found while trying to evaluate issue 167026 ...

NB 6.7 RC3, JDK6u14 64b and Ubuntu 9.04 64b
- run IDE with new userdir
- create J2SE Project
- create package FD
- create new "Bean Form" - extend javax.swing.JComboBox -> name MyComboBox (change background to green)
- compile this file
- created new JFrame in another package
- added MyComboBox into JFrame in design mode
- refactored FD packge to FieldData
- tried to open JFrame in design mode
-> design Error dialog risen ... so compiled MyComboBox once again
- changed background to blue
- compile MyComboBox
- added another MyComboBox into JFrame
-> see attached screenshot (there is evident difference ... and incorrect background shows in design mode, as well as in
preview ... in comparison to Running frame)
Comment 1 Marian Mirilovic 2009-06-13 21:08:37 UTC
Created attachment 83544 [details]
screenshot
Comment 2 Jan Stola 2009-07-21 13:19:22 UTC
The described behaviour is as designed. The form is not reloaded everytime some class (used by the designer) changes. 
When a component is added then a most recent class is used to create a new instance. When a preview is created then a 
new class is not loaded - the existing instance is cloned. The user can always reload the form (using Reload Form 
action on the root node in Inspector window) or close/reopen it when (s)he would like to force form-reload.
Comment 3 Marian Mirilovic 2009-12-03 03:25:57 UTC
v/c