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: | Move class refactoring breaks Design UI | ||
---|---|---|---|
Product: | java | Reporter: | _ pkuzel <pkuzel> |
Component: | I18N | Assignee: | issues@java <issues> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | issues |
Priority: | P3 | ||
Version: | 4.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
_ pkuzel
2005-03-16 15:57:15 UTC
Confirmed, accepted. I think the suggested behavior is a bit tricky. Actually if you move the form and keep entries in the original file then it will work. You moved the properties entries manually - but I'm not sure we should expect people knowing and doing this. IMO there is no good way to fix this - other than making the GUI builder automatically manage the properties entries and move them together with the form. This works best with the Swing Application Framework where the location is defined always relative; the automatic internationalization feature from NB 6.0 also assures the entries are moved with the form (integrated with refactoring). *** This issue has been marked as a duplicate of 48288 *** |