Since the deletion makes the code of the deleted method red
in the browser, the user knows they need to click to update
this browser. Hence, as Adriaan has noted, this is not too
serious; we should find an elegant solution or live with it.
It can be fixed by changing the #handleError: method's
behaviour in the case where a proceedable warning has a
parameter and the user returns a nil response to the
confirmer.
- The simpler fix is always to refresh the display of the
receiver of #handleError: in that case. The argument would
be that when the user choose to proceed via the third
response, a refresh after they have completed will always be
legitimate and often needed.
- The alternative is to make the #handleError: receiver the
parameter of the third option's block. I would like to leave
such a change until we discover a more explicit need for it
(The AddMethodChange can be given a reference to the
controller but this updates the code window, not the
navigator - see e.g the final lines of
BrowserTextTool>>compileMethodText:from:.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=753646
Since the deletion makes the code of the deleted method red
in the browser, the user knows they need to click to update
this browser. Hence, as Adriaan has noted, this is not too
serious; we should find an elegant solution or live with it.
It can be fixed by changing the #handleError: method's
behaviour in the case where a proceedable warning has a
parameter and the user returns a nil response to the
confirmer.
- The simpler fix is always to refresh the display of the
receiver of #handleError: in that case. The argument would
be that when the user choose to proceed via the third
response, a refresh after they have completed will always be
legitimate and often needed.
- The alternative is to make the #handleError: receiver the
parameter of the third option's block. I would like to leave
such a change until we discover a more explicit need for it
(The AddMethodChange can be given a reference to the
controller but this updates the code window, not the
navigator - see e.g the final lines of
BrowserTextTool>>compileMethodText:from:.