Puser wrote:
Yes.
I tried to be clear as much as possible in my first question.
No offense but I took a wild guess of what you wanted as it was totally not clear to me
We'll see what we can do, but not in the upcoming version. It's also something we don't like to do, as it could quickly lead to projects 'accidentally' not being generated because they were disabled the last time and someone forgot to re-enable them again. So it's a serious breaking change, usability wise, and we have to think about it.
(edit) A better solution would be to determine if an element in a derived model was changed since the last generation and if so, generate code for that model and not for the other models. And make that optional (disabled by default). But that too has plenty of pitfalls so it's not as simple as it looks. (The entity model is enabled always and that'll likely stay that way)