RE: What changes to the project does it want to save?
RE: What changes to the project does it want to save?
- Subject: RE: What changes to the project does it want to save?
- From: "Alexandre Fabre" <email@hidden>
- Date: Tue, 24 Jan 2006 10:18:21 +0100
- Thread-topic: What changes to the project does it want to save?
Hi,
xcode think that xcode local proj settings are locked because the
project.pbxproj
inside the project package is locked. But xcode try to save loacal
settings ( like
window position, "Groups & Files" preferences, toolbar configuration,
etc ... )
So if you want to save yout environment settings by project, you have to
- checkout the project
- change your settings
- then close xcode ( there is no error message asking for loosing
changes )
- undo checkout
- re open your project
It's borring, but a little better than xcode loosing some project
modifications without saying anything when closing a project.
Alexandre
------------------------------------------------------------------------
-
>> Like I said, only the .pbxproj is NOT checked out, so it does not
have
>> write permission. Yes, that's done by Perforce.
>>
>> The next time this happens (and it will the next time I work) I'm
>> going to go ahead and check out the project, let Xcode save whatever
>> it thinks it needs to save, then compare all the files in the
>> .xcodeproject with their previous revisions. At least that way I'll
be
>> able to see what Xcode is trying to change. If it's only user space
>> settings, that's a bug and I'll write it up.
I too am a Perforce user and this annoys the hell out of me. Though it
isn't quite so annoying as changing a lot of settings in the project,
then closing it without any warnings only to find that that the project
file was write-protected and all of my changes were lost. This happened
with beta builds of Xcode 2.2 and caused me a lot of lost time.
I did file a bug on the original beta 2.2 behavior and I'm glad that we
at least have warnings now, but I am annoyed when it warns me even
though I haven't made any changes. I even checked (like you said you'll
do next time) to see if it was making any changes to the project file
and it wasn't.
So a better solution would be for Xcode to see if it really is going to
change the project file and then only post a warning when there are
changes that might be lost.
_____________________________
Dave Thorup
Software Engineer
email@hidden
_______________________________________________
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