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.
It is possible to change modifiers or parameters of a method using its properties and the refactoring is not invoked. On the contrary it is not possible to change the method name at all using the method properties. Probably, if the user wants to change a method name or parameters using the method properties, the refactoring dialogs should be shown after clicking on [...] button.
For 4.0 we will probably disable the modification of those properties. We can consider invocation of the refactoring as an enhancement for the future. Honzo, can we make those properties read-only?
1. modifiers are customizable as a r/w node property - it is ok IMO since refactoring offers nothing special in this case. In the property customizer you can change access + others(final, static, ...). The refactoring permits to change just the access(visibility). It does not prevent you to change public -> private even if it breaks the code. 2. method parameters are already r/o node property. It is a bug of the associate customizer that it makes an impression you can add something. The Add button should be disabled. Nevertheless your changes are not applied to code. So this should be fixed in nb 4.0. 3. You can also change return type and exceptions as the node properties. Again, refactoring offers nothing special in these cases. We agreed on this with gtichy when we worked on the ui spec for jdk 1.5 features. IMHO, we should reconsider these properties as a whole. I propose to get rid of them at all in nb 4.1. Who edits code via them? The editor is the place where you type the code so why to traverse the explorer in order to invoke refactoring? I simply see no value in visualizing source code in the property sheet.
Honzo, please set target milestone. Thanks
no opinion from HIEs?
Fine summary Honzo and I agree, that we should consider to remove this Property dialog for method at all in the next release. PS: There are two properties which could be moved close to a code: Exceptions ... Could be invoked from suchlike Proactive Suggestion popup menu (Which exists already in Eclipse or Idea). Javadoc Comments ... There is another way how to invoke AutoComment tool or it could be added as a new toggle button in the Editor's toolbar.
Dusan, what is the result of your consideration? Have you updated the ui spec?
AFAIK responsible xDesign engineer is Rudolf Bock.
*** Issue 53376 has been marked as a duplicate of this issue. ***
Great, so hopefully Rudolf will project xDesigner's considerations to some document, preferably ui specification.
*** Issue 47449 has been marked as a duplicate of this issue. ***
I agree with Dusan Pavlica
The methods have no property sheets anymore.