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.
| Summary: | Changing model of JComboBox or JList generates wrong code | ||
|---|---|---|---|
| Product: | guibuilder | Reporter: | Josef Kozak <jkozak> |
| Component: | Code | Assignee: | Josef Kozak <jkozak> |
| Status: | CLOSED FIXED | ||
| Severity: | blocker | ||
| Priority: | P4 | ||
| Version: | 3.x | ||
| Hardware: | PC | ||
| OS: | Windows ME/2000 | ||
| Issue Type: | DEFECT | Exception Reporter: | |
::: absolutely reassigned ::: absolutely started If there is NO value (default) for model, the code should not be generated. ::: fixed in dev only verified in [nb_dev](20010718) Resolved for 3.3.x or earlier, no new info since then -> closing. |
Steps to reproduce: 1. create JFrame with JComboBox or JList 2. set property model e.g. to: a, b, c 3. set property model back to: null 4. bad code is generated -> there are 2 possible ideas (if user enters null): A. null will be accepted as default value of property, so NO code should be generated B. null will be accepted as the first string in StringArray of model, so code should be generated with one string value "null" More useful is A. in my opinion, null string value of model is not frequent used. If this will be needed, user could enter this value through ComboBoxModelEditor ("..." button).