• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode 2.1 saving lag
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 2.1 saving lag


  • Subject: Re: Xcode 2.1 saving lag
  • From: "Karan, Cem (Civ, ARL/CISD)" <email@hidden>
  • Date: Wed, 15 Jun 2005 10:48:44 -0400
  • Thread-topic: Xcode-users Digest, Vol 2, Issue 276

Code-indexing maybe?

I have a couple of C files that are autogenerated by another tool that are in the 5MB range that are always a pain to muck around with because the moment I save, I have to wait for the indexing to take over.  A possible solution to this would be to use an interactive, incremental parser (see http://www.cs.uwaterloo.ca/~elahav/meddle.pdf) so that code sense only needs to work on the parts that changed, rather than the whole thing at once.

My US$0.02 worth,
Cem Karan

------------------------------

Message: 7
Date: Wed, 15 Jun 2005 08:25:48 -0400
From: Tim Conkling <email@hidden>
Subject: Re: Xcode 2.1 saving lag
To: Robert Tillyard <email@hidden>
Cc: XCode Users <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

FWIW, I've seen this behavior as well. I now always pause for a few
seconds after saving a file to build it. The funny thing is, I have
the preference set to save all unsaved files before building.

Tim

On Jun 15, 2005, at 4:36 AM, Robert Tillyard wrote:


> I have a slightly different issue, I think that Command-S is saving
> in a separate (slower) thread. If I fix a syntax error and do a
> Command-S quickly followed by Command-B the build will stop at the
> same error despite the fact that the source is now different and
> the Window is showing that it has been saved. If you build again
> the error is fixed.
>
> Regards, Rob.
>
> On 15 Jun 2005, at 03:40, Rosyna wrote:
>
>
>> Since I grew up using Microsoft Word and the like, it's become
>> second nature for me to press command S to save every few seconds
>> (instinctively). However, since upgrading to Xcode 2.1, I've
>> noticed a huge lag whenever I said. I even get the spinning beach
>> ball. Is there some new setting in Xcode that causes it to do
>> something wacky and compute intensive on save?
>> --
>>
>> Sincerely,
>> Rosyna Keller
>> Technical Support/Holy Knight/Always needs a hug
>>
>> Unsanity: Unsane Tools for Insanely Great People
>>
>  _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: Shark complains: No sampling configurations found
  • Next by Date: Re: gcc 4.0 begins complaining of "redefinition of typedef 'foo'
  • Previous by thread: Re: Xcode 2.1 saving lag
  • Next by thread: Re: Re: Xcode 2.1 saving lag
  • Index(es):
    • Date
    • Thread