MDG Elements vs. Version control

[floerio]

Hi there!

We are using MDG technology to define, besides other things, elements for attributes and methods of classes. They are placed in the toolbox and then dopped by the user to add them to a class.

So far so good. Everything works as expected.

Now the problem: Our model is under version control. If now the user drops e.g. an attribute element on a class that is not locked by him EA does NOT raise any error but allows this addition. Only when he then tries to modify the atttribute afterwards with the "normal" property dialog he gets an error. But then the attribute is already added...

If he tries to add an attribute via the prop-dialog of the class, using the "attribute" dialog EA behaves correct by displaying an error "object locked" message.

Does anybody knows of this behavior?

Cheers.
   Oliver

[Geert Bellekens]

Oliver,

Although I don't use the MDG technologies I'm not surprised.
I've found several other occasions where EA didn't notice that an element should be read-only and allowed changes.
It seems to work a little bit better when using an integration with a VC rather then using the build-in locking mechanism alone.
Also when using the API you have to check the read-only status yourself for anything other then Elements.

Please report as a bug because these kind of things can get us into a lot of trouble (e.g. lost work).

Geert

[floerio]

Hi Geert,

thx for your answer. I will try to find the button to post it as a bug :-)

Cheers,
   Oliver