On Jan 20, 2008, at 3:46 PM, Christiaan Hofman wrote: >>>> True; the unarchiving can be done on the thread, though, after - >>>> init >>>> has returned. It would just cut down on overhead in case of >>>> multiple >>>> huge indexes stored on disk, so you wouldn't have to read all of >>>> them >>>> fully in order to find the right one. >>> >>> Of course unarchiving on the thread would mean creating the index on >>> the thread. And then we need safeguards in -index. (in the cancel >>> method the lock is probably sufficient). >> >> I'd say just creating it as a local variable and then assigning to >> the >> ivar when it's done is sufficient. The BDSKSearch now ignores a NULL >> index (but it won't get any delegate messages until the index is >> fully >> created anyway), so -index should be fine as-is. > > No that does not work. Apart from a failing OBPOSTCONDITION and a > log, sometimes it does nothing.
What does not work? And what sometimes does nothing? ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bibdesk-develop mailing list Bibdesk-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
