• 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.2 common error
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XCode 2.2 common error


  • Subject: Re: XCode 2.2 common error
  • From: Kieran Kelleher <email@hidden>
  • Date: Fri, 31 Mar 2006 20:41:28 -0500

Ah, I understand what you are saying now. For a second there I thought you were alluding to a way to revert to the old behaviour of having the individual errors show up in the "message" pane of the main XCode window instead of the single "jam failed" message and having to switch to Build Results to see the error details. I liked the old message pane behaviour, but I guess the new behaviour will be just fine after a day or two of pressing Command-Shift-B.

It's nice to see that CodeSense has improved from version 1.5 ..... now we get the static constants and methods of object superclasses showing up in code-sense ... finally we can advantage of the static XXX_KEY values generated by eogenerator.

Regards and thanks for going to the trouble of the screenshot and detailed explanation,

Kieran

On Mar 31, 2006, at 5:13 PM, Jerry W. Walker wrote:

Hi, Kieran,

If you see multiple panes in the build panel, notice a little dot that looks like an indentation in the center of the divider between the panes. If you have only one pane showing in the build panel, then look for the little dot immediately below the pane (in the frame).

<Picture 2.png>

Click and drag this dot to open up another pane or change its size. If you have an Editor pane showing, then when you click on an error in the top pane, the class containing the error will open in the build panel's Editor pane, highlight the line containing the error and scroll the text so the line is in the center of the pane. By closing the editor pane, you will get this same behavior in the code Editor in your main Xcode window.

Regards,
Jerry

On Mar 31, 2006, at 4:19 PM, Kieran Kelleher wrote:

Hi Jerry,

Thanks for the tips ... I just upgraded from XCode 1.5 to 2.2.1 ...... I don't understand the last sentence. What is the "indent button"? Are you talking about getting all the errors in the message pane of the main window like XCode 1.5 used to (which is what I would like to have again)?

Regards, Kieran

On Mar 31, 2006, at 6:31 AM, Jerry W. Walker wrote:

As a final tip, if you drag the indent button down to close up the editor pane in the build panel, Xcode will display the class and error in its normal code editor pane in the main window.



--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial Strength Internet Enabled Systems


    email@hidden
    203 278-4085        office




_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >XCode 2.2 common error (From: ".::welemski::." <email@hidden>)
 >Re: XCode 2.2 common error (From: "Jerry W. Walker" <email@hidden>)
 >Re: XCode 2.2 common error (From: Kieran Kelleher <email@hidden>)
 >Re: XCode 2.2 common error (From: "Jerry W. Walker" <email@hidden>)

  • Prev by Date: Re: XCode 2.2 common error
  • Previous by thread: Re: XCode 2.2 common error
  • Next by thread: Re: XCode 2.2 common error
  • Index(es):
    • Date
    • Thread