Oh well, off to Radar to file a bug on the Find panel, and I'll
figure out some sort of solution. I can probably use NSCharacterSet
or something and look at the characters on either side of the found
text. I was hoping to avoid that, but it looks like I can't.
You should still be able to build on doubleClickAtIndex: to determine
word boundaries at either end of your search string and in the found
text, and then implement whatever boundary-matching semantics you
choose on top of that, without having to use NSCharacterSet or
anything of the sort. Word boundary detection is complicated enough
(cf. UAX #29, "Text Boundaries", at http://www.unicode.org/reports/tr29/)
that you really don't want to have to implement it yourself.
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