🚀 go-pugleaf

Nik--
 
I've done this, but I did it for a former employer, so I have a feeling finding
and releasing the source code could potentially get me into trouble.  (I could
do it anyway, as long as you promised not to know where you got it, but even
here we might have problems.)
 
I think it's kind of interesting that Apple hasn't yet provided their own
windoid WDEF (digression:  I really hate the term "windoid"!) with this feature
in it.  This user-interface element is so common now that it seems natural to
include it.  I know that certain foreign script systems have to have this
window type to display their input methods.
 
Equally annoying is that there is no documentation on doing the color stuff.
There's a Tech Note that describes the current format of the 'wctb' resource.
But this is only half the problem.  The standard WDEF doesn't use the colors in
the wctb; they calculate the colors they do use from the ones in the wctb.  I
had to look at the WDEF source code to find the algorithm, and I never did
figure out how to translate the algorithm into C, copying the assembler
instead.  This is a BIG hole in Apple's documentation.  Apple, if you want us
to support your approach to window-frame coloring in our own WDEFs and CDEFs,
we need ALL the information!  Specifically, we need the algorithm used to
calculate the real colors to be published, along with which parameters are used
to get all the actual colors used in drawing the window frame.  Making us
figure all this out ourselves isn't developer-friendly.
 
Rich Gillam
GE Information Services