Re: How do you use Xcode 3?
Re: How do you use Xcode 3?
- Subject: Re: How do you use Xcode 3?
- From: Jerry <email@hidden>
- Date: Sat, 4 Oct 2008 17:10:47 +0100
On 3 Oct 2008, at 22:28, Seth Willits wrote:
On Oct 3, 2008, at 10:50 AM, Leo Revzin (Zevrix Solutions) wrote:
- The Code Sense:
I couldn't find a way to make it work like in Xcode 2.x, that is to
show the pop-up menu with suggestions every time you start typing a
word. For me, the new way Code Sense works in Xcode 3 is
unpredictable, unreliable, user-unfriendly and counter-productive.
Until Xcode 3, I have not used Code Sense since v1. I hated it then
because it worked wonkily, so I turned it off. I turned it back on
with v3 because my fingers were begging me to, and sometimes it
seems to work great. It offers suggestions, shows partial
suggestions when there's more than one possibility, and generally
doesn't seem to get in my way. But other times, it won't offer
suggestions at all, or completes an entire word, when there were
actually a few possibilities, so I have delete a few characters and
press escape to get it back into completion mode. And it'll behave
differently at different times when typing the same word.
So I agree. It's unpredictable. I can't just motor along and have it
do what I want, or even adapt to what it wants. Instead of I have to
wait and see what it's going to do before I can move on.
I agree. It's so unpredictable that I never use it - it's just quicker
to type a symbol name than see if code sense will complete it or not.
The same goes for Command-double click on a symbol: It takes you to
the right place maybe half the time, the rest of the time it takes you
somewhere completely random or does nothing. As a random example, I
have an enum with about twenty definitions. About half of these are
coloured and work with Code Sense, of the rest, some are completely
ignored if I click on them and the rest take you somewhere to a line
with a similar, name on it. It also seems to behave differently on
different machines with the same project and has a habit of crashing
Xcode while indexing, so it's best avoided. It's pretty well
impossible to file bugs on these though as small projects seems to be
fairly well-behaved and the bad projects are always big and top secret.
Jerry
_______________________________________________
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