• 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: Code Sense in 1.5
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Code Sense in 1.5


  • Subject: Re: Code Sense in 1.5
  • From: Andy Wiese <email@hidden>
  • Date: Sat, 13 Nov 2004 02:48:50 -0600


On Nov 12, 2004, at 5:37 PM, Shawn Erickson wrote:


On Nov 12, 2004, at 3:33 PM, Shawn Erickson wrote:


On Nov 12, 2004, at 11:57 AM, Allan Hoeltje wrote:

I've installed xcode 1.5 from the CD and slowly getting accustomed to the ui
changes. But I can't seem to turn on Code Sense.


It should be pretty clear: References->Navigation->Code Sense Apply.

But for some reason this does not turn on Code Sense. Is there a secret
hand shake I don't know about?

Sorry it is not clear from the above but is...

"Enable indexing" checked?

...and is...

"Enable code completion" checked?

The first one turns on indexing of your code, the second turns on the use of this index to help complete code as you type (either automatically or by keys sequence depending on other settings).

Also how do you know it isn't working? What are you looking for it to be doing?

I also meant to note that you can see (and/or change) the key bindings used to trigger code sense completion, etc. by clicking on the "Key Bindings" preference panel and then looking under "Text Key Bindings" and then "Text Editing".


-Shawn


I definitely have a problem with CodeSense. It finds completions from the system frameworks, and finds member variables defined in the file I'm currently editing. It never finds anything in my own code outside of the current file, and doesn't find functions or class names even in the current file. I wonder if it is related to the relative file path bug (where paths for project files that begin with ../ cause error marks to mess up). F&C also doesn't work, as far as I can tell.


Sooner or later I will rearrange my project files to experiment with this.

_______________________________________________
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


References: 
 >Code Sense in 1.5 (From: Allan Hoeltje <email@hidden>)
 >Re: Code Sense in 1.5 (From: Shawn Erickson <email@hidden>)
 >Re: Code Sense in 1.5 (From: Shawn Erickson <email@hidden>)

  • Prev by Date: Re: Code Sense in 1.5
  • Next by Date: can't locate file -lcrt1.o
  • Previous by thread: Re: Code Sense in 1.5
  • Next by thread: Re: Code Sense in 1.5
  • Index(es):
    • Date
    • Thread