troubles and complaints
troubles and complaints
- Subject: troubles and complaints
- From: Frank Rimlinger <email@hidden>
- Date: Sat, 3 Jan 2004 17:11:47 -0500
When I am building java code, red x's will appear in the gutter next to
lines of code where there is a compiler error. Upon rebuild, the old
x's will remain even if the error has been fixed. This is not the case
with C++ compiling/building. The only way I can get the x's to
disappear from java code is to do a clean. I can hardly imagine this
is a "feature". Does anyone else see this problem?
Also, I have noticed the x's will "smear" if you edit a file containing
them, so they no longer point to the correct line. It is also the case
that when "navigating" an edited file, the navigator does not take into
account the editing and so often selects the incorrect line. The
debugger has a similar problem, but that is forgivable. The other
cases are not.
Why is there no way to "deep open" in the debugger window? In cases of
even moderately nested class hierarchy it becomes tedious in the
extreme to keep having to open up every single drop flag.
When you type a global name into the expression window, nothing
happens. You don't get to see its value as advertised.
Why is there no diff mechanism like in CW? I know there is supposed to
be one build into CVS, but that is a lifetime of hardship and study to
set up.
Why is the "Project Symbols" window such a disorganized lump of
information?
And finally, why is syntax highlighting so lame? Variables and such
should turn to the correct color when spelled correctly.
frank
PS Happy New Year!
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.