_MeaningForwards/Backwards placement

[qwerty]

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.

[Paolo F Cantoni]

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!

[qwerty]

I don't recall (getting old, y'know). But I'll send that request. Probably futile but hope dies last.

q.

[Paolo F Cantoni]

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

But it DOES seems like a good way out of a questionable design issue.

Paolo

[qwerty]

Ah yes, your last post there. Now that you point me at it... :-)

q.