>Why this ain't hot.
>As the code is now in your application resource:
>1/ your are duplicating propriety code unnecessarily, and I'm also
>   not sure about the legality
>2/ any system wide changes - ie. themes, kaleidoscope, tinges - will
>   not apply to your WDEF
>3/ if Apple revises this WDEF in subsequent versions, your code can't
>   take advantage of this revision

What _I'd_ do, given the WDEF "must" be a given ID... after checking to 
make sure Appearance Manager is active, etc., in my initialization 
routine, I'd check to verify that there was a WDEF 66 in my resource 
chain. (In the System file, one would assume.)

Given all the pieces, I'd then create a "temp file" in the "temporary 
items" folder that contained only a resource fork, and I'd copy WDEF 66 
to it as WDEF 8. Then I'd put that temp file on my resource chain and go 
from there; deleting the file on exit. That would take care of any 
concerns about distributing Apple code (it's already on the Mac where 
we're running), and would pick up any revisions Apple makes. I'm not sure 
about how themes would work on it.

"Think different!" :-)

Bill