Default Package in V5.03

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

Default Package in V5.03

Keith  Lander
In v4 and earlier I'm sure that after setting the default package all new
classes were added to it. Maybe I'm missing something because, in the latest
version, that no longer seems to happen: in the new class dialog I now have
to select the correct package - why isn't the default pre-selected for me.
What is the default package for?

Regards
Keith


Reply | Threaded
Open this post in threaded view
|

Re: Default Package in V5.03

Blair McGlashan
Keith

You wrote in message news:b42l73$mme$[hidden email]...
> In v4 and earlier I'm sure that after setting the default package all new
> classes were added to it. Maybe I'm missing something because, in the
latest
> version, that no longer seems to happen: in the new class dialog I now
have
> to select the correct package - why isn't the default pre-selected for me.
> What is the default package for?

The intention is to completely retire the Default Package "mode" in a future
release. In D5 its original purpose (that of assigning a package for any
newly added classes, but not any other source object such as methods and
resources) has been superceded by the option to assign a package from the
new class dialog. This works to best effect from the System Browser (in DSE
and DPRO), as in that case if one is browsing a single package, then that
package will be the default choice in the dialog, regardless of superclass.
When adding a new class in the CHB then the dialog defaults to the package
of the superclass.

The default package mode remains in D5 for the purpose of capturing the
content of a file-in from a chunk file into a package, including any new
"loose" methods. This will be replaced in a future release by having a
package "context" for the file-in, rather than a global mode.

Regards

Blair