I have been experiencing the same thing in b5 -- about two seconds for
TM to actually become active again after switching away. I thought it
might be my file size or number of files open or something but I can't
find a direct correlation that is consistent. Two seconds on a dual
2.5GHZ G5 is an awful lot of instructions...
I'm curious, does this happen each time you switch
away and back to
TM, or only when something has actually changed in the filesystem?
Since things change on my filesystems all the time, I can't really say.
It seems pretty consistent, though.
Is there some experiment we could perform, something to profile to give
you some hints?
S
On May 7, 2005, at 6:31 PM, Allan Odgaard wrote:
> On May 7, 2005, at 22:26, Tom Lazar wrote:
>
>> I realize this has been discussed a while back, but AFAIR the issue
>> at the time has supposedly been resolved (threading of the
>> filessystemchecking process)
>
> No -- the threading mentioned in release notes is for loading bundles.
>
>> the project contains well under a hundred files, each moderately
>> sized, nothing fancy there. is there anything I can do on my side of
>> the problem? could you on yours, Allan?
>
> Long term, it should be fixed -- short-term you can change to a static
> project, i.e. instead of dragging a folder into the project drawer,
> drag the files form the folder. Of course you lose the advantages of
> folder references.
>
I'm curious, does this happen each time you switch
away and back to
TM, or only when something has actually changed in the filesystem?
>
> ______________________________________________________________________
> For new threads USE THIS: textmate(a)lists.macromates.com
> (threading gets destroyed and the universe will collapse if you don't)
>
http://lists.macromates.com/mailman/listinfo/textmate
>
>
Stephen F. Steiner
IDC
ssteiner(a)integrateddevcorp.com
www.integrateddevcorp.com
(603)433-1232