Re: Crasher due to unsafe block implementation in -[NSTextView checkTextInRange:types:options:]?
Re: Crasher due to unsafe block implementation in -[NSTextView checkTextInRange:types:options:]?
- Subject: Re: Crasher due to unsafe block implementation in -[NSTextView checkTextInRange:types:options:]?
- From: Kyle Sluder <email@hidden>
- Date: Thu, 11 Aug 2011 14:44:23 -0700
On Wed, Aug 3, 2011 at 3:32 PM, Aki Inoue <email@hidden> wrote:
> Another approach is to use multiple field editor objects so that you keep the first editor content unmodified.
That's not really an option in this situation. Our users' documents
often consist of thousands of rich text cells. Creating one field
editor per cell—which would be necessary since AppleScript can drive
multiple UI actions per runloop iteration, and we can't even be sure
that one runloop iteration is "enough" for the autocorrection block to
execute—would be prohibitively expensive, and we have taken great
pains in our products to carefully hook up our NSTextStorages to the
shared field editor in a way that conforms to the API.
In the meantime, we have completely disabled autocorrection in our
applications by removing the autocorrection flag from the bitmask.
Hopefully the bug in NSTextView is fixed soon.
--Kyle Sluder
_______________________________________________
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