SystemBrowser behavior in Dolphin 5.1.4

Hello,

I have noticed that he SystemBrowser behaves different than I would have
expected in regards to the package assignment of methods:

1. The first issue is that I cannot reassign the package of methods that
    do not belong to the package(s) currently selected. I wanted to
    change the package of a method to the current package. Why is
    the "Package" function in the method context menu disabled for
    those methods?

2. The other issue relates to the package assignment of copied methods
    in the SystemBrowser.
    I have a little "test" project with its own package. That package
    also contains some loose methods for class Number.

   - I display my package "test" in the SystemBrowser and select the
     Number class.
   - When I open a 2nd ClassBrowser or SystemBrowser, select a
     method #xzy of a class "Foo" and drag it into the Number class in
     my 1st browser for copying, the method Number>>xyz is assigned
     to the package of the class (in my case package "Dolphin" of the
     class Number).

     However since I did this action with package "test" as the only
     selected package in the SystemBrowser, I would have expected that
     the copied method in class Number would be also assigned to
     package "test" as a loose method.
     When I create the method directly for class Number, it is correctly
     assigned to my selected package "test", it's only when I apply
     drag and drop that this doesn't work.

Both issues are just minor gripes, but a solution particularly for
issue #2 would be appreciated.

Best Regards,
Bernhard Kohlhaas

Bernhard,
"Bernhard Kohlhaas" <[hidden email]> wrote in
message news:[hidden email]...
[...]
> 1. The first issue is that I cannot reassign the package of methods that
>    do not belong to the package(s) currently selected. I wanted to
>    change the package of a method to the current package. Why is
>    the "Package" function in the method context menu disabled for
>    those methods?
IIRC, you can get around this with a combination of shift-drag (i.e., move)
and the Default Package feature (see below).

> 2. The other issue relates to the package assignment of copied methods
>    in the SystemBrowser.
>    I have a little "test" project with its own package. That package
>    also contains some loose methods for class Number.
It may not be exactly what you want, but if you right-click on a package in
the system browser or package browser, there's a Set as Default Package item
(it's an on/off toggle).  If you select it for a package, the package name
shows in bold, and new methods (etc.) are added to that package, regardless
of which package contains the class that owns the method.

HTH,

Don

Don Rylander wrote:

Thank you very much. That workaround works nicely. :)

Bernhard