RE: Xcode 4 related questions
RE: Xcode 4 related questions
- Subject: RE: Xcode 4 related questions
- From: Jeff Laing <email@hidden>
- Date: Wed, 16 Mar 2011 00:51:44 +0000
- Acceptlanguage: en-US
- Thread-topic: Xcode 4 related questions
> Even with a regression like that I'd call it much improved. Have you filed a
> bug report about this particular issue? It would be great if you could!
>
> <http://developer.apple.com/bugreporter/>
Not yet.
I've been too busy getting my projects building again.
I *will* report it, but I'm as jaded as everyone else in this space, having had my share of reports disappear into the pit.
What annoys me about this particular issue is that it took me ONE SINGLE time to actually use that field to realize that it was clearly unacceptable. Clearly, whoever implemented it at Apple either (a) didn't test it (b) didn't think it mattered (c) noticed it and reported it, so my bug report will go into the same duplicate pile as always.
What worries me more is that they missed significant usability issues.
I have two Xcode 3 projects, both of which have imported a third project that creates a useful framework that I share into them. (Actually, more than one but for this email, lets say one).
If you try to open them both side-by-side with Xcode 4, it gives an error message in the second that suggests something has gone catastrophically wrong whereas its clearly getting locking issues on the shared component, that the first has opened successfully.
Anyone who works on a shared library that they use in multiple products is going to want to make changes, test how the changes impact their various deliverables, repeat until done. You just can't do that with Xcode4 without merging all your products into a single workspace, which is not acceptable for anything but the most trivial of product sets.
_______________________________________________
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