I tracked down why your models were marked as dirty ... I didn't have
a variation on addSortOrdering in EOFetchSpecification that
suppressed event notification. So during a model load, when it was
adding its sort orderings initially, those were firing events making
the UI think the model was being modified. I just committed a fix
for that and I'm able to open a model with fetch specs without it
appearing to be dirty.
ms
On Jul 17, 2006, at 5:47 AM, Pierre Frisch wrote:
> Hi Mike,
>
> I have done a few test to see how the editor behave when saving and
> why I get all my models as "dirty".
>
> I think this has to do with the fetch specs. When I save one of my
> models it erase the value in the fetch spec. Apart from the layout
> that change because of the different plist serializer the problem
> is with the value dictionary in the qualifier. The key "_key" is
> missing. I think the problems lies with
> org.objectstyle.wolips.eomodeler.model.EOKeyValueQualifier when
> serializing and deserializing the value line 105 and 130 is
> referenced as "name" instead of "_key".
>
> Pierre
>
> Before the save:
> name = {
> class = EOFetchSpecification;
> entityName = AdStatus;
> fetchLimit = 0;
> isDeep = YES;
> qualifier = {
> class = EOKeyValueQualifier;
> key = name;
> selectorName = "isEqualTo:";
> value = {"_key" = name; class = EOQualifierVariable; };
> };
> refreshesRefetchedObjects = YES;
> sortOrderings = (
> {class = EOSortOrdering; key = position; selectorName =
> "compareAscending:"; }
> );
> };
> After the save:
> name =
> {
> refreshesRefetchedObjects = Y;
> fetchLimit = 0;
> sortOrderings =
> (
>
> {
> key = position;
> class = EOSortOrdering;
> selectorName = compareAscending:;
> }
> );
> class = EOFetchSpecification;
> qualifier =
> {
> key = name;
> value =
> {
> class = EOQualifierVariable;
> };
> class = EOKeyValueQualifier;
> selectorName = isEqualTo:;
> };
> entityName = AdStatus;
> isDeep = Y;
> };
>
This archive was generated by hypermail 2.0.0 : Mon Jul 17 2006 - 15:04:52 EDT