Eric,
It's possible that NSTextFinder has a bug, in which case you should file a
Radar with a sample app that reproduces the problem. Having that information,
it may be possible to identify a workaround.
However, first tell me—are you setting the endsWithSearchBoundary parameter to
YES for the
I'm using the NSTextFinder API with the stringAtIndex:len:effectiveRange: style
of exposing the text.
I have a test case which has 4 strings in it, "foo1" .. "foo4". I show the
findbar, type 'foo', and click the 'find next' control.
Here are the calls that my client receives and the results be
