On Jul 31, 2010, at 8:31 AM, Tony Romano wrote:
> Here is one additional thing I discovered. I have an outlet to the
> NSTextField that contains the cell so I can write text to it. This is the
> only connection to my application. If I remove the outlet, the
> drawingRectForBounds: is called
Here is one additional thing I discovered. I have an outlet to the NSTextField
that contains the cell so I can write text to it. This is the only connection
to my application. If I remove the outlet, the drawingRectForBounds: is
called. If I add it back, it won't get called. Why should havin
@interface ViewStatusTextCell : NSTextFieldCell
- (NSRect)drawingRectForBounds:(NSRect)theRect;
@end
- (NSRect)drawingRectForBounds:(NSRect)theRect
{
NSRect rect = [super drawingRectForBounds:theRect];
NSSize textSize = [self cellSizeForBounds:theRect];
NSUIntege
On Fri, Jul 30, 2010 at 3:38 PM, Tony Romano wrote:
> I have an NSTextTextField in my nib that is using a custom NSTextFieldCell
> (set in IB) class that has only one method over-riden, drawingRectForBounds.
> The method is not being called. This is what I have done.
>
> 1. Set a break point
I have an NSTextTextField in my nib that is using a custom NSTextFieldCell (set
in IB) class that has only one method over-riden, drawingRectForBounds. The
method is not being called. This is what I have done.
1. Set a break point to verify it is not being called.
2. Using F-Script, verified
