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.
We should emphasise in the docs that the user must NOT compile the class manually before he issues "Fix&Continue". If he does that, the class will not be updated. See Issue #40440.
I'll update the Fix topic. Also adding as a relnote since this is a change from 3.5.
Created attachment 13758 [details] copy of fixed Fix file
fixed in trunk. Maros, could you please verify? I also made a few other small changes that I want to make sure are correct.
I read through the Fix documentation and found 2 minor inconsistencies. 1) "Modify your code and save the changes." ... you don't have to save the file 2) "If the most recent call belongs to the changed class, an alert box is opened." ... the alert box is opened only if you modify the currently executing method, ie. you may change other methods in the same class freely
Maros, would the following changes suffice? < <li>Modify your code and save the changes. --- > <li>Modify your code. 61c61 < If the most recent call belongs to the changed class, an alert box is opened. --- > If you have modified the currently running method, an alert box is opened.
Yes, that's ok.
fixed
the fix is in release36; will be merged back to the trunk after code freeze