Re: Xcode 4 isn't always able to jump to analyzer warnings
Re: Xcode 4 isn't always able to jump to analyzer warnings
- Subject: Re: Xcode 4 isn't always able to jump to analyzer warnings
- From: Quincey Morris <email@hidden>
- Date: Tue, 19 Apr 2011 17:20:42 -0700
On Apr 19, 2011, at 16:27, G S wrote:
> It it's intended, it's a design error. The source code that the messages refer to has been deleted, and that deletion affects ALL schemes. Why would it ever be correct to refer to nonexistent code?
I think you're being a bit disingenuous. In Xcode 3, the Build Results window is out of date as soon as you start editing the source again, but that doesn't necessarily mean you want the Build Results window to disappear in a puff of smoke as soon as you hit a key. For that matter, in Xcode 3, error and warning bubbles in the source files themselves don't disappear instantly when you resume editing. (That's so, isn't it? Xcode 3 seems so long ago now I'm not sure I remember exactly what it does.) To some extent, that's what's going on here, in Xcode 4.
The other thing to keep in mind is that "bug cross-talk" can prejudice your opinion of a design choice. There are still *many* situations in Xcode 4 where error messages disappear early, or linger too late, for unrelated or unknown reasons. (In particular, I've seen errors from previous builds sometimes disappear on editing the source line, and sometimes not.) It's way too easy to make harsh usability judgements on buggy behavior. (I've been known to yell "But it's a *bug*!!!!" at colleagues who forget 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