Re: Xcode 3, hide warning "bubbles"?
Re: Xcode 3, hide warning "bubbles"?
- Subject: Re: Xcode 3, hide warning "bubbles"?
- From: kwiley <email@hidden>
- Date: Mon, 11 Feb 2008 12:54:37 -0800
On Feb 11, 2008, at 12:15 PM, Chris Espinosa wrote:
On Feb 11, 2008, at 10:26 AM, kwiley wrote:
Xcode 3 does this inline error/warning thing where it litters the
source code with red and yellow bubbles that are actually
*inserted* into the source code display. Furthermore, this is done
with bright ketchup and mustard backdropped rounded-rectangles that
are extremely visually distracting. In the Build Results window
there is a button that turns off display of all the warnings and
removes these bubbles, but I can't find a way to get rid of them in
the source code windows or the editor without manually clicking
each individual gutter icon.
How the heck do I get rid of them? I searched the Xcode docs for
"hide warnings" and got nothing.
The generally preferred way to get rid of annoying warnings and
errors is to fix your code. That's why they're intrusive.
Click the Help menu, type "bubble" into the Search bubble, and it
will show you the menu items that control message bubbles.
Chris
If you're volunteering to fix thousands of deprecated library calls
for me, give me a ring we'll set it up. I won't pay you though, but
the project is worth almost no money (well, I'll give you ten bucks if
you actually get it done). If you don't think that sounds like a very
good deal, then you understand why I'm not willing to fix the
warnings. It' as simple as that. Either agree to fix them for me for
no payment or retract your suggestion. It's one or the other. :-)
For my part, this is an ancient legacy project that worth virtually no
money and only minimal maintenance time. I'm not going to spend a
month of my life updating it to modern libraries. I will however help
it limp along until it keels over, because it *is* worth just about
that much effort/time/money. For example, bringing the code into a
new Xcode 3 project and tweaking it to build on a Leopard Intel mac
took me about half and hour. That was work worth doing because the
project is worth perhaps a half hour of monkey-wrenching. Gutting the
deprecations on the other hand is a fundamentally illogical suggestion
because redesigning, reengineering, and rewriting the project from
scratch would probably be more efficient in terms of time spent or
overall mental anguish than updating the existing code.
...<sigh>...I just knew someone make this sort of comment when I asked
the original question. I anticipated and cringed as I hit the Send
button. Thanks for validating my fear...
Thanks for the tip on the bubbles by the way. Someone else pointed
out that the settings are in the prefs but I didn't realize they were
in the menus too. That's great to know.
Cheers!
________________________________________________________________________
Keith Wiley email@hidden http://www.cs.unm.edu/~kwiley
"And what if we picked the wrong religion? Every week, we're just
making God madder and madder!"
-- Homer Simpson
________________________________________________________________________
_______________________________________________
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