It's not intended to be an accurate statement. The point is to avoid
jumping to conclusions. Framework code is far more exposed than your
own, and it is immensely more likely that you've screwed up than the
Quartz devs have.
I get that. I just don't think that's necessarily a good place to
make that assertion. :-) My younger self spent hours on a bug I was
sure was mine because it couldn't possibly be the API ... it was the
API. :-)
If you have an app where a "column" is a first-class conceptual
model, for example, you might need a more interactive header cell ...
There be dragons.
You mean like OmniOutliner? :)
I realize you work at Omni Group, so you see my point. :-) It's far
from trivial to get this stuff heavily customized until you've spent a
long time doing just that.
Still - I own a copy of OmniOutliner registered to my real name - I
see that the column headers (beyond a different drawing style) really
only add right-click-to-show-context-menu action. That simple approach
works perfectly for OmniOutliner, but I can think of more complicated
scenarios where more direct interaction with the header itself would
be the most natural approach ... *There* be dragons. :-D
This is where I was coming from. Then I looked at the stack trace and
saw NSLayerKitGlue. He might not be doing anything complicated, but
AppKit is.
All I was saying there was that it's not really possible to assign
a difficulty level as we don't really know what the OP is trying
yet. :-)
A note: Positively no disrespect intended.
--
I.S.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
