On 13 Dec 2012, at 23:17, Kyle Sluder <k...@ksluder.com> wrote:
>
> Since I'm comparing the string-drawing methods to NSTextFieldCell
> drawing, according to this documentation there should be no difference.
>
In my test case I compared the cells rendering with an NSTextField configured
as a label.
@implementation MyTextFieldCell
- (void)drawInteriorWithFrame:(NSRect)cellFrame inView:(NSView *)controlView {
NSStringDrawingOptions options = 0;
if (self.truncatesLastVisibleLine)
options |= NSStringDrawingTruncatesLastVisibleLine;
if (!self.usesSingleLineMode)
options |= NSStringDrawingUsesLineFragmentOrigin;
NSAttributedString *attString = [[NSAttributedString alloc]
initWithString:self.stringValue];
[attString drawWithRect:[self titleRectForBounds:cellFrame]
options:options];
}
@end
I tried the following uber simple implementation above and it doesn't produce
the same rendering as a standard text cell.
The custom implementation is a couple of pixels offset to the left plus the
font weight and kerning is slightly different.
So the implementation used by NSTextFieldCell obviously isn't the same as this.
The cell is free of course to offset the text frame as it sees fit prior to
actual text rendering.
e.g.: when drawing complex cells with images etc it is necessary to introduce
offsets between the rendered elements.
The docs for drawInteriorWithFrame:inView: say:
Text-type NSCell objects display their contents in a rectangle slightly inset
from cellFrame using a global NSText object.
Is that offset accessible via the API or related to titleRectForBounds:?
The docs for titleRectForBounds: say:
If the receiver is a text-type cell, this method resizes the drawing rectangle
for the title (theRect) inward by a small offset to accommodate the cell
border. If the receiver is not a text-type cell, the method does nothing.
But surely the cellFrame received by drawInteriorWithFrame:inView: has already
accounted for the cell border, or is this another interior border?
So I think this might be an implementation guessing game.
If the rendering issue is comparative (i.e.: the custom render looks bad
compared to the default in say a table view) then a solution might be to use
the custom implementation everywhere.
Jonathan
_______________________________________________
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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
