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: | Renaming variable in guarded block should invoke refactoring | ||
|---|---|---|---|
| Product: | guibuilder | Reporter: | Milan Kubec <mkubec> |
| Component: | Code | Assignee: | issues@guibuilder <issues> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | ||
| Priority: | P2 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Bug Depends on: | 48288 | ||
| Bug Blocks: | |||
| Attachments: | screenshot | ||
|
Description
Milan Kubec
2005-08-12 13:32:38 UTC
Created attachment 23759 [details]
screenshot
Form module should be able to handle this. Hear hear. If you need to rename a field declared in a form, it is at best a 2 step process - refactor and rename, folloed by rename in the form. If you are unlucky, it is more steps than this because you have to then rename the field in every code snippet. This is tedious and error prone. Hear hear. If you need to rename a field declared in a form, it is at best a 2 step process - refactor and rename, folloed by rename in the form. If you are unlucky, it is more steps than this because you have to then rename the field in every code snippet. This is tedious and error prone. I think this is duplicate for issue 48288, or not? Have no strong opinion about this. Can be considered a duplicate of 48288 in the sense that we need to make the GUI builder cooperate when refactoring happens. OTOH initiating the refactoring from GUI builder can be viewed as an additional request. In either case, 48288 must be done first. Done together with issue 48288. |