2 small suggestions about saving methods

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

2 small suggestions about saving methods

Chris Uppal-3
Would it be possible to have a global option to warn me when I'm saving a
method under a new name that would overwrite an existing method ?

Not as easy as it sounds, I suspect, since there are a number of places (and
not all of them instances of MethodBrowser) from which methods can be saved.

Also, what do people think should happen when saving a loose method under a
new name ?  Currently the new method gets added to the class's package.  I
think it might be better if it got added to the same package as the original
method.  (In much the same way as it gets added to the same method
categories).

    -- chris


Reply | Threaded
Open this post in threaded view
|

Re: 2 small suggestions about saving methods

Blair McGlashan
"Chris Uppal" <[hidden email]> wrote in message
news:[hidden email]...
> Would it be possible to have a global option to warn me when I'm saving a
> method under a new name that would overwrite an existing method ?
>
> Not as easy as it sounds, I suspect, since there are a number of places
(and
> not all of them instances of MethodBrowser) from which methods can be
saved.

I think it might be quite tricky. I'll record it as an enhancement request.

>
> Also, what do people think should happen when saving a loose method under
a
> new name ?  Currently the new method gets added to the class's package.  I
> think it might be better if it got added to the same package as the
original
> method.  (In much the same way as it gets added to the same method
> categories).

Coincidentally we were discussing that very thing this morning and had
decided to do it that way in D5 (which now preserves the package of loose
methods copied/moved by Drag & Drop).

Regards

Blair