Xmo'd is not creating files based on the current model version #37

Closed
74monkeys opened this Issue Nov 10, 2010 · 4 comments

Comments

Projects
None yet
2 participants
@74monkeys

I have just added a new model version, and set it as current.
When I make changes I get no updates happening on the generated files.
If I make changes to the old model version and save them, I do get changes in the generated files.
I looks like it is tracking the wrong model version - it's odd as it is tracking version 3, and now I'm on 4, so it's not like its always following the first version.

@74monkeys

This comment has been minimized.

Show comment Hide comment
@74monkeys

74monkeys Nov 10, 2010

More investigation has discovered the following.

If you add "xmod" to the comments of the model (ie, select the model in the groups & files browser, not the individual model versions below) this does not appear to autogenerate.

If you select the model in the groups and files and then select the specific model version file in the details view, and add xmod to that comment, then that version will be generated.
So if you update the version you have to remove the xmod comment from the old version file and add it to the new version file.

This doesn't sound like this is how it should work ?

More investigation has discovered the following.

If you add "xmod" to the comments of the model (ie, select the model in the groups & files browser, not the individual model versions below) this does not appear to autogenerate.

If you select the model in the groups and files and then select the specific model version file in the details view, and add xmod to that comment, then that version will be generated.
So if you update the version you have to remove the xmod comment from the old version file and add it to the new version file.

This doesn't sound like this is how it should work ?

@rentzsch

This comment has been minimized.

Show comment Hide comment
@rentzsch

rentzsch Nov 10, 2010

Owner

That's how it works, by design :-) I require the xmod comment tag on a specific version to eliminate ambiguity. It would be nice if you could just have the xmod comment on the model group instead of a individual model and rely on the "current version", but IIRC the AppleScript for that is painful/impossible. Patches welcome if you want to pursue that feature.

Owner

rentzsch commented Nov 10, 2010

That's how it works, by design :-) I require the xmod comment tag on a specific version to eliminate ambiguity. It would be nice if you could just have the xmod comment on the model group instead of a individual model and rely on the "current version", but IIRC the AppleScript for that is painful/impossible. Patches welcome if you want to pursue that feature.

@74monkeys

This comment has been minimized.

Show comment Hide comment
@74monkeys

74monkeys Nov 10, 2010

Ok, now I know !
Thanks for the reply.

Ok, now I know !
Thanks for the reply.

@rentzsch

This comment has been minimized.

Show comment Hide comment
@rentzsch

rentzsch Feb 16, 2011

Owner

This adds support for auto-latest-version detection: #46

Owner

rentzsch commented Feb 16, 2011

This adds support for auto-latest-version detection: #46

seanm pushed a commit to seanm/mogenerator that referenced this issue Jan 6, 2012

Merge pull request #46 from vguerci/mogenerator
---

This pull request allows to put `xmod` tag on a versionned model *(.xcdatamodel**d**)*
Script then will automatically detect current version and call `mogenerator` on it.

This modification is non intrusive and not breaking existing behavior.
This is a popular request related to several issues : #7, #14, #37

Thanks to nvie who this is largely inspired from : nvie/mogenerator@5755843

ddrccw pushed a commit to ddrccw/mogenerator that referenced this issue Jan 20, 2014

Merge pull request #46 from vguerci/mogenerator
---

This pull request allows to put `xmod` tag on a versionned model *(.xcdatamodel**d**)*
Script then will automatically detect current version and call `mogenerator` on it.

This modification is non intrusive and not breaking existing behavior.
This is a popular request related to several issues : #7, #14, #37

Thanks to nvie who this is largely inspired from : nvie/mogenerator@5755843

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment