Yes, I've run into this before. I think the reasoning is that, if you do not copy down the superclass implementation, this is not truly a refactoring—it will change the behavior of a selector that was already understood by the siblings. But I agree that in many cases, this change of behavior is the desired outcome and having the option would be good. The simplest change would be to add a "Cancel" button, and make the "No" option do what you want—perform the refactoring without adding the extra methods. Perhaps adding a warning to the text of the dialog like "Choosing 'No' may modify behavior." (ideally more detailed but I'm having trouble phrasing it concisely).
On Sat, Jun 28, 2025 at 10:54 AM Aik-Siong Koh <as...@askoh.com> wrote: > > > There are two questions, but only response accepted. > I just want a pull up with nothing extra done. > If I click yes, I get the extra methods. > If I click no, nothing at all happens. > > Please advise, > Thanks, > Aik-Siong Koh >
