Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!well!wdh
From: wdh@well.UUCP (Bill Hofmann)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Window classes
Message-ID: <12208@well.UUCP>
Date: 15 Jun 89 16:26:11 GMT
References: <3949@hacgate.scg.hac.com> <32367@apple.Apple.COM> <5202@pt.cs.cmu.edu> <5209@pt.cs.cmu.edu> <2478@molokai.sw.mcc.com> <2480@molokai.sw.mcc.com>
Reply-To: wdh@well.UUCP (Bill Hofmann)
Distribution: usa
Organization: Whole Earth 'Lectronic Link, Sausalito, CA
Lines: 18

In article <2480@molokai.sw.mcc.com> dorsett@molokai.sw.mcc.com (Robert Dorsett) writes:
>What is Apple policy on using the WindowKind field of a window record to
>store information on application window classes?  IM V. I only says that TWO
>classes are defined, yet reserves an entire word for the function.
I don't know what Apple policy is, but here's my understanding:
If you want the Desk Manager to deal with a DA window properly, you have
to put the negative refNum into the windowKind field (actually, -(refNum+1)).
If you want the Dialog Manager to deal with a window properly, you have
to put dialogKind (2) into the windowKind field (this is done automatically
by NewDialog).  Thus, if you have a DA window which you use dialog manager
calls on occasionally, you'll have to swap windowKinds.

Other than that, there's no restriction on the use of windowKind.  I use
it to identify various kinds of windows, and find it rather handy.  There's
no programmatic interface, and I've never found anything that depends on
the windowKind being userKind (8).

-Bill Hofmann