<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Sep 16, 2007, at 2:12 PM, tim Rowledge wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Costumes are in my opinion one of the more useful parts of the tweak design. You an change the look by changing the costume.</FONT></P> </BLOCKQUOTE></DIV><BR><DIV>Perhaps - but when wanting to make a custom control - it gets unclear (to me anyway) whether one should subclass one or both of the player/class pair. This is the bit I expect people to get wrong often. </DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>An example is the multi-column Mac OS X file browser - I sat down to try to make one of these a couple different times and never really got anywhere as I kept going around and around on whether I should just keep the existing file chooser player, but make a new costume, or make a new player to go along with it.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Having once built an event based system that relied on a pair of threads separated by a queue - I can see how debugging things can be a pain as you don't have that nice stack to figure out just how you got here.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>-Todd Blanchard</DIV></BODY></HTML>