Sparx Systems Forum
Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: qwerty on July 22, 2021, 05:45:18 pm
-
Metaclass or stereotype. That is the question. How about both? If those two (and likely a few more) properties could be respected from both sources? With the metaclass taking precendence? Wouldn't that be cool? So I could (still) have a general metaclass used by multiple stereotypes and define these properties therein. And for a single stereotype I could overwrite them with some individual setting.
What are dreams for: being shattered?
q.
-
Metaclass or stereotype. That is the question. How about both? If those two (and likely a few more) properties could be respected from both sources? With the metaclass taking precedence? Wouldn't that be cool? So I could (still) have a general metaclass used by multiple stereotypes and define these properties therein. And for a single stereotype, I could overwrite them with some individual setting.
What are dreams for being shattered?
q.
As you may recall I already suggested that. Send a feature request, if they get more than one, they might act!
-
I don't recall (getting old, y'know). But I'll send that request. Probably futile but hope dies last.
q.
-
I don't recall (getting old, y'know). But I'll send that request. Probably futile but hope dies last.
q.
It was buried in... Custom MDG _UCRect appears not to work (https://www.sparxsystems.com/forums/smf/index.php/topic,46020.msg269648.html#msg269648)
But it DOES seems like a good way out of a questionable design issue.
Paolo
-
Ah yes, your last post there. Now that you point me at it... :-)
q.