This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi there, Useability for the inheritance feature: Let me mark a property as the descriminator property. Ensure only one property within the class is marked as descriminator property. At the inheritance association display that property instead of let me typing it. While saving the model, check for doublicated descriminator values at the inheritance associations You ask for it :-) - Sörnt |
|
|
Hi Soernt, Thanks for another nice suggestion! I've implemented this a little differently to what you suggested. As of the next nightly build, an entity has a new Discriminator property. You can fill this in for an entity that's going to be a base class. Then whenever you add a new derived class to the hierarchy, we will initialise the Discriminator Name and Type from the root class Discriminator. Note that this is *initialisation*: if you change the root Discriminator, that *won't* automatically update any existing derived classes. And it's still the arrows that count: the root class Discriminator property is just to save time setting up the arrows. I've also added some checks for multiple discriminators in the hierarchy. At the moment, these produce warnings rather than errors, but I can't think of a scenario in which multiple discriminators would work, so I may up these checks to errors in the future. Feedback welcome! |
|
|
Hi Ivan, thanks for implementing this feature! I just found the time to do some testing of it. The initialisation is working fine :-) I would like to get a validation check (while saving) for doublicated "Discriminator Value"s. For example, two children can't have a discriminator value of "0" - it's likely that I forget to set a valid value. Cheers, |
|
|
Done and will be in the next nightly build. |
|