On Tuesday, July 21, 2009, Kyle Sluder <kyle.slu...@gmail.com> wrote:
> Remember, 90% of the time, the bug is in your code. The other 10% of > the time, the bug is in your code. That's just not true. Plenty of bugs in the frameworks. I've personally logged dozens. It's USUALLY your code but certainly not always. > There aren't any. It's not a hard class to work with. Except when it is. Why so many absolutes? Try customizing table views / columns / header views / etc. I mean beyond setting a custom data cell or adding keyboard actions. Some of these mechanisms work in unexpected (and sometimes conflicting) ways. Not all of This behavior is documented either. It's not insurmountable but it's far from easy. Tables are fairly complicated UI. 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. As to the OP's problem, however, I suspect the real issue is probably pretty simple since he did not mention heavy customization. Could be wrong though ... -- 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