XCode overzealous external editor support...
XCode overzealous external editor support...
- Subject: XCode overzealous external editor support...
- From: Tom Harrington <email@hidden>
- Date: Thu, 2 Jun 2005 10:27:58 -0600
When I was using XCode 1.5 I noticed the behavior where XCode would
ask if I wanted to save changes on documents that weren't actually
open in XCode, and that weren't part of any project open in XCode.
Basically, if I tried to close a project in XCode while TextWrangler
or SubEthaEdit has a file open with unsaved changes, XCode will ask if
I want to save changes on the file-- in the process, intrusively
getting involved with other applications working on unrelated files
which XCode should neither know nor care about. And this when I don't
even have external editing support enabled in XCode.
I just wanted to mention that this problem persists in XCode 2.0 on
Mac OS X 10.4.1.
I've been going round and round with this with developer support-- I
filed a new bug describing the problem with XCode 2.0, but I can't
seem to get them to believe me. This is especially annoying since
someone from Apple acknowledged the problem on this list back in
February and encouraged me to submit a bug on the problem.
Developer support keeps asking for more information, but I don't know
what else I can possibly give them. They wanted me to submit a
project that would exhibit the bug, even though in my experience any
Xcode project at all will exhibit it. I did submit a detailed list of
steps to take to reproduce the project with the inital bug report, but
I have to believe that they're just reflexively demanding more
information without attempting to reproduce the problem. If they'd
taken two minutes to walk through the steps in the bug report, they'd
have seen the problem by now.
I guess I could just create a blank new project in XCode and send them
that, but I hate to resort to such bland stupidity against what looks
like an unwillingness to even try.
If anyone from Apple sees this and knows anything about this behavior
of XCode's, I'd really, really appreciate it if you could try and
knock some sense into the bug-reporting process regarding bug 4126882.
I suspect it's a duplicate by now, but who knows if developer support
will acknowledge it as such?
--
Tom Harrington
email@hidden
AIM: atomicbird1
_______________________________________________
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