Aki, > No, it doesn't chunk based on word boundary. > It could callback in chunks in order to prevent allocating too large buffer, > though. > > So, you should be prepare to insert whatever requested.
In fact, you're (of course) right. What I see is that it does cut as long as I keep typing in the field. But, when the field looses and regains first responder status, all the text is sent at once. Since I have to identify keywords in a flow of chars, I do the surgery (or butcher ;)) operation myself in my custom -(void)generateGlyphsForGlyphStorage:… method, generating multiple calls (one for each chunk) to the shared instance NSGlyphGenerator -(void)generateGlyphsForGlyphStorage:…, and I analyse the return product. Yet, I assume that – more or less in accordance to what the documentation says –, the shared instance glyph generator does a basic one to one translation between unicode and glyph, so that the length parameter in the callback -(void)insertGlyphs: length: is valid not only for the glyph buffer, but also for the original string. Is that hypothesis correct? Thanks a lot (and thanks also for the very informative talk you gave, without which I surely wouldn't have been able to figure out all this)! Vincent_______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
