Yeah, along the lines of getting the GUI to display code and code related stuff nicely, I'm having a royal pain of a time to get a project to RUN, have a console window open on one monitor, and ONLY the console and have my main code editing window open on the other.
Today I had 4 projects open and was toggling back and forth between them. Why can't Xcode 4 just be straightforwards and open a console window that is only a console window? Why must it also have some other window's properties attached to it.
No, I don't want the debugger to attach to it. No, I don't want it to be a child of a code window. I just want a console running Geneva 10 point so I can see my debug output and have the simulator running right next to it on one monitor while my other main window has my main code window and debugger.
Why is it so hard to simply open a window that is the the NSLog outputs and have it ONLY be the window that gets the NSLog outputs?
BTW, when the debugger appears, am I missing something painfully obvious, or does the debugger only show you the properties of each variable, but not the values you actually want to see? I end up having to NSLog out all the values of my dictionaries and arrays since the summary is always out of scope. Is there a way to actually have the only thing I care about - the KVP values - listed in the debugger?
On Mar 22, 2012, at 11:46 PM, Luther Baker wrote: Hey GS,
Why all the off-topic commentary and denigration?
-Luther
On Thu, Mar 22, 2012 at 10:08 PM, G S <email@hidden> wrote:
Not a bad request, William, but yes the first thing I thought was, "Oh man, there are so many things that need to be fixed before the Xcode team should be spending time on this."
And the team unfortunately tends to entertain every ill-founded objection to enhancements and make decisions that serve the tiny minority of use cases while crippling the majority of usage. For example, I asked that Xcode not insert garbage tabs or leading spaces on empty lines, something that Visual C++ doesn't do and yet offers equally effective auto-indent.
Someone actually argued that filling the files with this garbage is GOOD. And unfortunately, this is the kind of specious objection that routinely holds sway at Apple. Witness the lack of even an option to keep files sorted. So I'm sure someone would step up with an objection to William's request, and that would be that.
Hey, speaking of leading garbage on empty lines, can Uncrustify strip this out?
_______________________________________________
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
- Alex Zavatone
|