Problem with source list resolved

0 views
Skip to first unread message

Bill Garrison

unread,
Dec 10, 2009, 1:22:53 PM12/10/09
to syracuse-are...@googlegroups.com
Although my attempted demo of my mysterious source-list-data-not-
display problem was a bust last night, I finally figured out what was
causing it in the one project that would consistently fail.

Corrupted user default property lists. Somehow, the preferences
property list for the project that was failing got hosed. And that's
where the autosaved window size+location data is kept.

~/Library/Preferences/com.company.yourproject.plist

I did a directory comparison in FileMerge between the failing and
working project, scouring the code for differences. Finally, it
dawned on me that those preferences plists were also involved.

rm -r ~/Library/Preferences/com.company.*

Problem resolved. *smacks forehead on desktop repeatedly*

Now You Know™

Bill

Michael Fey

unread,
Dec 10, 2009, 1:44:43 PM12/10/09
to syracuse-are...@googlegroups.com
Glad to hear it! I take it that the user defaults dictionary doesn't get corrupted every time, right?
> --
>
> You received this message because you are subscribed to the Google Groups "Syracuse Area CocoaHeads" group.
> To post to this group, send email to syracuse-are...@googlegroups.com.
> To unsubscribe from this group, send email to syracuse-area-coco...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/syracuse-area-cocoaheads?hl=en.
>
>

Bill Garrison

unread,
Dec 10, 2009, 9:21:19 PM12/10/09
to syracuse-are...@googlegroups.com

On Dec 10, 2009, at 1:44 PM, Michael Fey wrote:

> Glad to hear it! I take it that the user defaults dictionary
> doesn't get corrupted every time, right?

That seems to the case. I haven't had any problems since clearing the
preference files out. The corruption probably happened once during
development, a crash just as the file was being written or something.

Seems to be consistently fine now.

Bill
Reply all
Reply to author
Forward
0 new messages