Re: Why must [NSLayoutManager lineFragmentRectForGlyphAtIndex:effectiveRange:] be computed twice?
Re: Why must [NSLayoutManager lineFragmentRectForGlyphAtIndex:effectiveRange:] be computed twice?
- Subject: Re: Why must [NSLayoutManager lineFragmentRectForGlyphAtIndex:effectiveRange:] be computed twice?
- From: Gerd Knops <email@hidden>
- Date: Thu, 27 Dec 2007 11:47:22 -0600
On Dec 27, 2007, at 6:09 AM, Ewan Delanoy wrote:
The surprising thing is, to make my code work I have
to execute
[myLayoutManager lineFragmentRectForGlyphAtIndex:myGlyphIndex
effectiveRange:NULL] twice in order to get the correct result.
Is this on Leopard? In a complex application have a problem which I
suspect might be related: Opening a document from within
applicationDidFinishLaunching: causes some text paragraphs to be drawn
incorrectly. If I use a timer to have the document opened just a hair
later, it draws fine. This was not a problem in Tiger.
I spent many hours to no avail trying to narrow it down to either fix
it or at least be able to file a useful bug report.
Gerd
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden