FROM : Douglas Davidson
DATE : Wed Nov 27 22:06:32 2002
On Wednesday, November 27, 2002, at 12:46 PM, Chris Ridd wrote:
> My app is basically plunking a different NSString into a non-editable
> (multiple fonts not allowed) NSTextView when the user clicks on rows
> in a
> NSTableView.
>
> All's fine and dandy, except that I've noticed that after I put one
> particular string into the view, all subsequent strings get displayed
> in a
> *slightly* bigger font. By bigger I mean slightly less condensed,
> perhaps a
> slightly bigger font size. The guilty string is this (gibberish, and by
> \uxxxx I mean Unicode character xxxx):
>
> "\u2662\u2663\u2661\u2660\n\u2022 point\n\u20AC89"
>
> I'm just using setString: to drop each NSString into the text view,
> and I'm
> not using attributed strings anywhere so I am not expecting any font
> changes.
>
> Has anyone else seen anything like this?
setString: applies the typing attributes to the string. The typing
attributes are normally derived from existing text. In this case, your
text requires a different font to display it, and this is getting into
the typing attributes.
If you really don't care what font is used, you can do what you are
doing, i.e. never specify a font and let the text view figure one out
for itself. If you do care, then set the font yourself, either via the
NSTextView, by calling setTypingAttributes: or setFont:, or else by
operating on the NSTextStorage and setting a font attribute there.
Multiple fonts not allowed merely means that the user is not allowed to
set multiple fonts. Programmatic changes are a different matter.
Douglas Davidson
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
DATE : Wed Nov 27 22:06:32 2002
On Wednesday, November 27, 2002, at 12:46 PM, Chris Ridd wrote:
> My app is basically plunking a different NSString into a non-editable
> (multiple fonts not allowed) NSTextView when the user clicks on rows
> in a
> NSTableView.
>
> All's fine and dandy, except that I've noticed that after I put one
> particular string into the view, all subsequent strings get displayed
> in a
> *slightly* bigger font. By bigger I mean slightly less condensed,
> perhaps a
> slightly bigger font size. The guilty string is this (gibberish, and by
> \uxxxx I mean Unicode character xxxx):
>
> "\u2662\u2663\u2661\u2660\n\u2022 point\n\u20AC89"
>
> I'm just using setString: to drop each NSString into the text view,
> and I'm
> not using attributed strings anywhere so I am not expecting any font
> changes.
>
> Has anyone else seen anything like this?
setString: applies the typing attributes to the string. The typing
attributes are normally derived from existing text. In this case, your
text requires a different font to display it, and this is getting into
the typing attributes.
If you really don't care what font is used, you can do what you are
doing, i.e. never specify a font and let the text view figure one out
for itself. If you do care, then set the font yourself, either via the
NSTextView, by calling setTypingAttributes: or setFont:, or else by
operating on the NSTextStorage and setting a font attribute there.
Multiple fonts not allowed merely means that the user is not allowed to
set multiple fonts. Programmatic changes are a different matter.
Douglas Davidson
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
| Related mails | Author | Date |
|---|---|---|
| Chris Ridd | Nov 27, 21:46 | |
| Scott Anguish | Nov 27, 21:56 | |
| Douglas Davidson | Nov 27, 22:06 | |
| Daryn | Nov 28, 00:45 | |
| Douglas Davidson | Nov 28, 00:57 | |
| Chris Ridd | Nov 28, 10:45 |






Cocoa mail archive

