Overriding NSTextLayoutFragment.draw(at:in:)
in an NSTextLayoutFragment
subclass provided by the NSTextLayoutManagerDelegate
is indeed the designated way of doing custom drawing now. However, note that it still doesn't have quite the same effect as NSLayoutManager.drawBackground(forGlyphRange:at:)
. While you can draw behind the text by doing your custom drawing before calling super.draw(at: point, in: context)
, all custom drawing in NSTextLayoutFragment
is still done above text text view's selection (in NSTextView
anyway). In NSLayoutManager
, drawing done in drawBackground(forGlyphRange:at:)
was done beneath the text selection, which could be useful for some elements. There seems to be no way of doing the same in TextKit 2 just yet. (I filed this as #FB10159592 but received a fairly standard dismissive reply).
You can also do custom drawing in NSTextView
's drawBackround(in:)
, but that's more awkward because calculating the visible ranges is expensive.
For custom interaction, I suppose it depends on what you're trying to do. You could do it in a text view subclass and use NSTextLayoutManager
's various methods to get the frames of the text you need. For instance, I allow live image resizing in an NSTextView
, and draw resizing handles over image text attachments. For that I can use NSTextLayoutManager
's layoutFragment(for: point)
in mouseDown(_:)
, converting the point from text view to text container coordinates, and I can then get the image frame using NSTextLayoutFragment.frameForTextAttachment(at:)
, and add a new sublayer to the text view to draw my resizing handles. There are a couple of gotchas here, though:
-
Because NSTextView
(and presumably UITextView
) in TextKit 2 does all of its drawing using layers, you have to set the z position of any new sublayer you add to something high (e.g.FLT_MAX
).
-
The coordinate system used for TextKit 2 is so far undocumented, and seems pretty strange. NSTextLayoutFragment.layoutFragmentFrame
is straightforward, being in text container coordinates, and NSTextLayoutFragment.renderingSurfaceBounds
is relative to that (although the docs say its coordinates are flipped compared to layoutFragmentFrame
, when they don't seem to be). However, both NSLayoutFragment.frameForTextAttachment(at:)
and NSTextLineFragment.typographicBounds
seem to be relative to NSTextLayoutFragment.layoutFragmentFrame
vertically, but relative to the text container horizontally. (And there are also some issues with the frames being narrower than you'd expect when using overlay scroll bars.)
I'm not sure how helpful that is to what you want to do.