🚀 go-pugleaf

David A. Rebnord writes
> While I would certainly agree it would be best for the dwrites to be  
> documented, they are not unknowable.  You can use DefaultMgr (available for  
> free at sonata (thanks and kudos to Drew Davidson) )

I could, but then I would get no idea of what dwrites were safe to use as far  
as NeXT is concerned.  Perhaps they stuck some in there just for their  
purposes, as they stick undocumented API in applications for their own use (for  
example, the famous bug seen by hitting the "Reply" button in NewsGrazer while  
mail is being edited in a non-miniaturized window(s) in Mail.app).  I would  
doubt that NeXT would want people (let alone give out) procedures or  
instructions that they felt uneasy about people using routinely or things that  
might cause problems for some users.

I'm not bitching at you at all, David Rebnord, but at NeXT:  Given that  
documentation was supposed to be included with 3.0 and this isn't documented  
*anywhere* in the docs for 3.0, I'd say NeXT should fix the situation by  
posting a list of safe dwrites to use (as well as other things that didn't make  
it into the on-line documentation for one reason or another) until they come  
out for everyone via a 3.1 software release (where 3.1 means the set of all the  
bug fixes known at the time of its release, additional documentation and  
_fully_ localized portions of NeXT apps as they promised).

Basically, while I agree that using DefaultMgr works to get the answers, I  
think complete documentation is the only definitive answer to this problem  
because I'd rather (and feel that I am fully justified to) hear it from NeXT.   
If it is the case that NeXT does not want people to use this, then I wouldn't  
expect to find it in the documentation (or the application, actually).  Since  
there are other things that are not documented but should be, I thought this  
was one of them.
-- 
-- Jeff (jeffo@uiuc.edu)
-- NeXTmail welcome