Re: No such file or directory
Re: No such file or directory
- Subject: Re: No such file or directory
- From: Thomas Engelmeier <email@hidden>
- Date: Wed, 22 Feb 2006 10:27:42 +0100
On a side note, the edit window in which the recursive checkbox is
buried exhibits random data entry behavior when trying to save
changes to the directory path text. It takes multiple attempts to
get it to save the text correctly.
Please file a bug at bugreporter.apple.com about any "random data
entry behavior." We don't have any current reports of this on file.
Probably because it
- is not straightforward reproducible (random is a good clue)
- IMO far to many bug reports come then back with "submit the
complete project" or "cannot reproduce within the first two clicks" -
the later also for as "random" or "never reproducible" filed bugs.
It might be OK to spend another hour to report an reproducible bug +
testcase where you found the trigger on the way to workaround, but it
might be a little much expected we spend another half of full working
day - likely to be 'spare'time or overtime - to make reproducible
trivialities from existing bugs. And then have the bug closed as
duplicate. Sorry, that is NOT my job.
The bug described by Jeff one was one of the minor issues setting up
15 subprojects and cost me and an fellow developer summed up - it
struck us maybe 5 times - approx. 1/2 day. The current workaround is
a xcconfig file that specifies all "common" include directories.
Much more of a time killer was the file + path handling (1 1/2 days
manual resetup + validation of imported CW projects - too much
unexpected behavior). I see only rare (single developer) occasions
where absolute paths make sense. As soon everything is relative,
there is no way to automatically adjust relative leaf paths when an
group root node gets assigned an path for the first time so that the
leaves entries have just the path {enclosing group}/filename.cpp.
Fixing that takes a lot of time where *cough* I'm not sure everyones
emotions are very positive. IIRC not reported due to 16h working days
to get the JOB DONE.
In the tasks before that, fresh imported CW projects had on my
machine completely messed up paths for file entries. They look fine
with "get info" but Xcode cannot find a single file.
Once I realized everything worked as soon as the Xcode project is
closed and reopened, that issue was settled for me.
Another issue with include directories et al. - Many, many times I
cannot "Command-D" open an user include file (even when Xcode manages
to find the header in order to switch between header & implementation
file). I frankly don't bother enough to report _that_ as long as
BBedit or CW with an shadow project opened in parallel do their job.
It bugs me more e.g. Interface Builder yesterday went three times in
an infinite loop on the attempt to move three textfields. Or Xcode
has an continuous red entry for an dylib that builds fine when the
destination path is changed in the target settings.
If the bug descriptions above (sans personal comments) had been
sufficient for bugreporter - as a base where problems are perceived
by the users - you'd already have them.
Regards,
Tom_E
_______________________________________________
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