I don't disagree that it might be preferable to have by-app
(or even by-inspector) defaults, but GLOBAL is definitely
one that should be setable from an inspector, or at least
recognized, since such recognition SHOULD be automatic...
3.2: /NextLibrary/ ... /ApB_Defaults/Defaults.rtf
<BLOCKQUOTE>
If the owner is *GLOBAL: (or *-g: for dwrite), the value will
apply to all applications except those that specifically own
another value for the parameter.
</BLOCKQUOTE>
The 'Scope' of GLOBAL defaults is not defined by virtue of their
being owned by the pseudo-application 'GLOBAL', but rather depend
upon their keyword. Any across-applications default where such
are not from the same creator or vendor are candidates for GLOBAL
usage. NeXT 'official' recognition would be nice, but in its
absense, the only requirement is that 'NX' not be the first two
letters (although it might be wise to avoid 'NS' and 'OS' as
well).
That's the way I see it.
Bruce
+-+
Bruce Gingery Total System Software Cheyenne, WY USA
We do consulting over Internet. E-Mail
tss@TotSysSoft.com for quotes or more info.
Homepage construction area:<URL:http://metro.turnpike.net/bagingry/>
NEXT IN LINE magazine staff technical writer
Bruce Gingery <bgingery@Wyoming.COM> OR <bruce@TotSysSoft.com>
Multimedia: NeXTmail(tm) preferred MIME-mail welcome