18
« on: June 13, 2022, 11:50:09 am »
While we, like some other organisations, haven't been able to upgrade to v16 due to an inheritance bug when defining models via the metadata[1] - we have been persevering with v15.2. We're noticing that when we use our model-generated QuickLinker definitions between certain stereotypes, some of the options go "walkabout" - that is, they disappear! Try to link to another stereotype (which should produce the same result and they are present!).
When this happens, our research occasionally finds there are (legitimate) behind-the-scenes reasons why EA decides not to provide the option. However, often, there seems to be NO "rhyme or reason" for this (that we can see).
So after spending a wasted two hours trying to establish any logical reason why the option was missing, we tried the SAME MDG specification on the SAME repository under v16 to discover that under V16, the options are "all present and accounted for"!
Can anyone, but preferably a Sparxian who can speak knowledgeably about the subject, indicate what inheritance improvements that affect the QuickLinker behaviour were made in the v16 release? Those of us who have been here a long time are aware that these explanations are often obfuscated under arcane descriptions of version changes. We'd like to understand clearly what has been improved so we can quickly decide that a new QuiuckLinker failure under v15 has been fixed in v16 rather than have to waste a lot of energy starting up v16, cross-checking and then determining that the issue still occurs under v16.
In addition, are there any more changes to inheritance under MDGs for the next release of EA?
Paolo
[1]We have since been told that the defect will be fixed in the next release.