I'm hitting a major performance bottleneck when using doubleClickAtIndex. I have one sample file (about 3MB) with 23,500 hits that require me to use doubleClickAtIndex: to test for whole words. It is essentially a find/replace on full words. One find all (with no replacement) operation takes about a 65 seconds to complete. Most of the time spent in memcpy. And that's only one of about 30 find and replaces to be done.
The same basic test using the FindPanel's ReplaceAll (with Full word option) takes under 1 second to complete on the same text. I thought I read that FindPanel was also using doubleClickAtIndex:. The performance difference seems to hint that it is not, or that I am missing something. Is the FindPanel's ReplaceAll (with full word) doing something different to calculate the word boundaries that makes it significantly faster than using doubleClickAtIndex? The doubleClickAtIndex: approach works fine on smaller samples of text, but seems unusable with a much larger sample of text. Is there a way to programmatically find "full words" with similar performance to NSTextView's FindPanel? Thanks. -- Mark Munz unmarked software http://www.unmarked.com/ _______________________________________________ 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 [EMAIL PROTECTED]
