Re: Subclassing NSToolBar.
Re: Subclassing NSToolBar.
- Subject: Re: Subclassing NSToolBar.
- From: Ali Ozer <email@hidden>
- Date: Fri, 5 Oct 2001 14:01:46 -0700
>
Absolutely. In which case our app would very likely break, and we'd
>
need to find either where the bits had moved, and/or need to implement
>
something else. We're aware of that and have chosen to use non-public
>
features of NSToolbar anyway. It's our own fault, and we promise not to
>
complain if/when you move them. :-)
Omni has always been responsive in these areas (whether or not the
breakage was Omni's fault or Apple's), which is great. However, it's
still the case that users don't enjoy having to update their apps on
every system release, and sometimes we decide we can't go ahead with
some fix or feature because the change ends up causing visible
compatibility issues in serious, shipping apps...
>
(I suppose a disclaimer on my original message would have been helpful,
>
but I thought it was fairly obvious that I was describing private bits
>
that could easily change and break.)
This list has many folks new to Cocoa, so clarification of what's
private and a bad idea to use and what's public is always useful I think!
Ali