Re: Changes to the layout of a .xclassmodel file are not persistent
Re: Changes to the layout of a .xclassmodel file are not persistent
- Subject: Re: Changes to the layout of a .xclassmodel file are not persistent
- From: Ray Kiddy <email@hidden>
- Date: Mon, 13 Jul 2009 11:32:56 -0700
On Jul 13, 2009, at 9:22 AM, Korei Klein wrote:
I'm trying to learn how to use xcodes design features to produce
a .xclassmodel file and I am running into this problem:
I created a classmodel. I dragged the boxes into a layout that I
liked, and saved the .xclassmodel file.
When I built my project, the boxes moved back into a layout that I
didn't like.
How do I get the boxes to stay where I put them?
_______________________________________________
They should be staying where you put them.
Are you sure that things are being saved? When you try to build, do
you always get a confirmation dialog asking if you want to save the
model file? If you do, that means something is going wrong in the save
of that file.
Also, when you save, the icon for the model file in the left-hand nav
bar should go from dark to light. Note that there are times when it
looks as though a file is selected, such as when it is selected in the
left-hand nav bar and it is visible in the edit window, when it is
actually not selected. When this happens, a cmd-S will send a save
command to something else. Usually, if you actually click in the edit
window, then the file is actually selected. This problem with Xcode
focus and selection constantly bothers me, but given that this has
been happening for 10+ years, there must not be too many of us.
Inside the "xcdatamodel", which is actually a directory, there are two
files, "elements" and "layout". If you note the modification time for
these files, and then build, do the modification dates change. If the
mod date for the layouts file changes, or if the layouts file is
getting deleted (whereupon it will be re-created), this would explain
what you are seeing. If this is happening, you should file a bug.
Or you can create a new project and put this projects stuff in that
new project. This may be a sort of random project file corruption
issue and these are usually too ephemeral or complicated to re-create
to get fixed. You could file and bug and include the bad project, but
don't hold your breath after that. Create a new project and you will
be able to move on.
cheers - ray
_______________________________________________
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