Refactoring bug ?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Refactoring bug ?

Bruno Brasesco
Hi,

If i use #remove (#myMethod) from Refactoring, and another method
(#secondMethod) "call" #myMethod.
I browse the references to #myMethod (in a MethodBrowserShell), and if I
delete this reference to #myMethod (inside the MethodBrowserShell, and I
"accept" it) the #secondMethod is not removed from MethodBrowserShell.

I do not know if it is a bug (missing the refresh), or it work in that way.

Best Regards
Bruno Buzzi Brasesco


Reply | Threaded
Open this post in threaded view
|

Re: Refactoring bug ?

Blair McGlashan
"Bruno" <[hidden email]> wrote in message
news:ab1kg4$ejh62$[hidden email]...
> Hi,
>
> If i use #remove (#myMethod) from Refactoring, and another method
> (#secondMethod) "call" #myMethod.
> I browse the references to #myMethod (in a MethodBrowserShell), and if I
> delete this reference to #myMethod (inside the MethodBrowserShell, and I
> "accept" it) the #secondMethod is not removed from MethodBrowserShell.
>
> I do not know if it is a bug (missing the refresh), or it work in that
way.

That's just the way it works at present. It could be changed to use a
dynamic filter, but to do so would require changes in the refactoring engine
code, which is something we are trying to minimize in order to make it
easier to intregrate the latest version of the Refactory engine.

Regards

Blair