On 4, Jul, 2012, at 03:22 PM, Marco Tabini wrote: >> Does anyone have any good suggestions as to how to update my search results >> when the underlying source text changes? Do I have to listen for all changes >> from the underlying text objects and try to adapt, or is there a better >> pattern for doing this? Xcode does this nicely: no matter what changes you >> make in the editor, the search results seem to be updated on the fly. > > Couple of random suggestions: > > * If you're using NSAttributedString, you can mark your search results by > assigning custom attributes to specific ranges of text; as the text changes, > those attributes will stick around and you can later find them using the > attribute retrieval methods (I believe that's what Xcode does).
Just a follow up on this. I guess I would have to clear all text attachements of a particular class from all files at the start of a search, right? Otherwise the attachments will build up over time. I don't actually save attributed text to disk (these are plain text files) but even so. Does that make sense? I wondering how computationally expensive this will turn out to be. Martin > > * As an alternative, a more naïve approach could be to simply repeat the > search every time you detect the text changing, but depending on the size of > your text files, that could eat up a lot of CPU cycles, and is just inelegant. > > I'm sure there are other possibilities, too, but these two are the first ones > that come to mind. > > HTH, > > > —Mt. _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
