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 23261 - Renaming JFrame does not carry thru to other generated code "[FFJ CUSTBUG]"
Summary: Renaming JFrame does not carry thru to other generated code "[FFJ CUSTBUG]"
Status: CLOSED INVALID
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: -FFJ-
Hardware: All All
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-08 23:11 UTC by kishm
Modified: 2007-09-26 09:14 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kishm 2002-05-08 23:11:26 UTC
"[FFJ CUSTBUG]"

When creating a JFrame using the JFrame template, the 
frame's name is set to JFrame - there's no way to specify 
a different name. 

If you later go to RENAME the class, the class definition 
line changes correctly, but the reference in the main 
method for this class remains unchanged. Should carry thru 
the rename throughout.

To reproduce the rename problem , create a JFrame, then 
right click and choose rename and give a different name , 
then open the code you'll see that only the class name is 
renamed , but not in the main method etc.
Comment 1 Richard Malaschitz 2002-05-09 13:21:27 UTC
When is creating JFrame using the JFrame template, you can specify name of new class. Only if you don't 
specify name, 'JFrame' is chosen.

Until now, when you can rename form, you must change method in main() manually in editor.
Comment 2 Tomas Pavek 2002-05-23 15:36:32 UTC
I think this is a problem (if it is a problem) of java 
module. Reassigning...
Comment 3 Svata Dedic 2002-05-23 19:40:55 UTC
It should be possible to specify a custom name for the newly created
object: either at the first panel when invoked through context menu on
the folder, or at the second panel when invoked through File | New. I
think that the default value for the name is "<default>" which is
translated to the template's own name. 

The rename works as designed, sadly. To trace & rename symbol
referencies NetBeans would need a machinery to find those; we are
still far away from implementing it (something may be ready in 4.0
release).
Setting to invalid, there's already numerous RFEs regarding this, no
need to create another duplicate.
Comment 4 Quality Engineering 2003-07-01 13:11:12 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.
Comment 5 Quality Engineering 2003-07-01 13:21:02 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.