Lyderic Landry wrote:
>I just don't see any reason for the system to keep nodes
>that have only key-less or child-less children, but this is just me.
On managed systems, I can see a possible reason.
The admin could create the base levels of a tree but forbid mundane users
from adding or removing those nodes. On Mac OS X, that could be done by
appropriate changes to ownership and permissions of the relevant files and
dirs. These restrictions would be in addition to the elevated privileges
needed to modify the system Preferences tree.
I'm not saying that this is the reason behind the Preferences design
decision, only that it's something that can be done when nodes aren't
auto-removed just because they're empty, yet would be precluded if nodes
WERE auto-removed on empty. The real reason might be something much easier
to understand, like plain old simplicity of design (absence of excessive
cleverness, aka anti-features).
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
