> On 7 Nov 2016, at 16:43, Alastair Houghton
> wrote:
>
> On 6 Nov 2016, at 06:18, Quincey Morris
> wrote:
>
>> There is probably no perfect strategy that works for every font. However,
>> for the kinds of design decisions
On 6 Nov 2016, at 06:18, Quincey Morris
wrote:
>
> 5. It’s rather indeterminate what glyphs the bounding box should reflect. In
> particular, in digital typography using Unicode characters, a font as
> perceived by the user may be a composite of multiple
> On 6 Nov 2016, at 13:18, Quincey Morris
> wrote:
>
> On Nov 5, 2016, at 21:44 , Gerriet M. Denkmann wrote:
>>
>> NSRect boundingRect = tableFont.boundingRectForFont;
>> self.outlineView.rowHeight = ceil(
On Nov 5, 2016, at 21:44 , Gerriet M. Denkmann wrote:
>
> NSRect boundingRect = tableFont.boundingRectForFont;
> self.outlineView.rowHeight = ceil( boundingRect.size.height )
This is probably a poor choice, for reasons that probably will seem illogical:
1. The
macOS 12.1 TableView and OutlineView (View Based) use:
- (void)awakeFromNib
NSRect boundingRect = tableFont.boundingRectForFont;
self.outlineView.rowHeight = ceil( boundingRect.size.height )
and sets attributedStringValue (using the tableFont).
This works mostly ok.
But for