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 44267 - Rename does not work in Form Editor guarder blocks
Summary: Rename does not work in Form Editor guarder blocks
Status: RESOLVED DUPLICATE of bug 48288
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: issues@guibuilder
URL:
Keywords:
: 51855 (view as bug list)
Depends on: 49294
Blocks:
  Show dependency tree
 
Reported: 2004-06-03 10:31 UTC by Martin Balin
Modified: 2005-05-13 16:37 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
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 Martin Balin 2004-06-03 10:31:07 UTC 
[Build 200406021800]
Rename does not work in Form's guarded block, 
but it proceeds elsewhere. This creates non 
compilable code.
Output window correctly marks lines in quarded 
block with red error message, but I will still 
expect that Refactoring works inside guarded 
blocks.
Comment 1 Jan Becicka 2004-06-03 11:27:24 UTC 
It is as designed. Were are unable to peform refactoring in guarded
blocks, because they are regenerated from .form files, which are out
of our control. I'm changing type of this issue to FEATURE.
Comment 2 Martin Balin 2004-06-04 09:54:45 UTC 
I expect that guarded blocks are there for user typing modifications 
and that you could modify this in cooperation with Form Editor. It 
looks like a design flaw in refactoring and editor together if 
refactoring cannot change guarded blocks for user.
Comment 3 Martin Matula 2004-06-04 10:01:20 UTC 
The guarded block *can* be changed by the refactoring. But even if it
would change it, the text would be regenerated (i.e. the changes would
be reverted) by the form editor as soon as the file would be open in
it since the real data are not in Java files. Changing guarded blocks
is actually much easier for us than detecting that they are there and
forbidding the change. But we had to choose the second option since
right now we are not finding usages in non-java files. This feature is
planned for the next release.
So, to sum up, guarded blocks usually signal that the data contained
in them are generated from the other source (which is unknown to the
refactoring module), thus changing the text in the guarded block is of
no help since the guarded block can be regenerated from the real
source anytime by its parent module.
Comment 4 Martin Balin 2004-06-04 14:31:54 UTC 
I know this. I just would expect that Refactoring can ask *that* 
module to perform rename in its real source. Ok, it is probably 
complicated for version 1.
Comment 5 Martin Matula 2004-11-09 13:10:31 UTC 
This should be addressed in 4.1.
Comment 6 Martin Matula 2004-11-26 20:06:19 UTC 
*** Issue 51855 has been marked as a duplicate of this issue. ***
Comment 7 Jan Becicka 2005-01-05 09:04:42 UTC 
Issue 49294 is fixed. Reassigning to Form module.
Comment 8 Tomas Pavek 2005-05-13 16:37:50 UTC 

*** This issue has been marked as a duplicate of 48288 ***