XCode 2.1 Errors and Warnings glitch
XCode 2.1 Errors and Warnings glitch
- Subject: XCode 2.1 Errors and Warnings glitch
- From: Emidio Cunha <email@hidden>
- Date: Mon, 3 Oct 2005 10:10:11 +0100
Hello all,
I've come across a very distressing glitch on xcode, related to the
Errors and Warnings smart group.
I've set up a small Objective-C foundation tool project, that simply
has 3 files in it, the main.m, and a couple of .h and m relating to a
class I've been testing.
Funny thing is, if I make a mistake on the .h file, and the main.m
file is *Closed*, errors and warnings works just fine, reporting the
error on the correct source file.
But, if main.m is *Open*, then at first when I look at the errors and
warnings list, I get the error location on the .h file and the second
I click it, it changes to the main.m file, pointing to the #import
line...
The build result window is the only reliable tool for handling errors
and warnings, the way I see it...
I tested this on a fresh install as well as an upgrade install, and
also, on two diferent projects, just in case.
I've looked everywhere on the lists, google, etc, seems like no one
has come across this, which is something I find hard to believe.
Thanks for any help.
Emidio
_______________________________________________
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