Here is the basic approach I'm using. I commented out the replace code
to focus on the the performance of the actual search. If I set the
granularity such that doubleClickAtIndex: is not used
(FindTypeContains), the performance is reasonable. Otherwise, the
performance is as described earlier. I bo
On Nov 5, 2008, at 9:37 PM, Mark Munz wrote:
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 no
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
