Association Class destroys "Composite"

[Paolo F Cantoni]

Before I report this a (yet another) bug.  Is anybody else experiencing this?

If you have a class marked composite (and therefore with an associated diagram), when you make the class an AssociationClass via <vertex context menu>|Advanced[ch9658]|Association Class..., the composite setting is removed.

AND... (to add insult to injury)

when you put the "composite" setting back, the:
<vertex context menu>|Advanced[ch9658]|Unlink Class and Association,
disappears to be replace by:
<vertex context menu>|Advanced[ch9658]|Association Class...which menas you can't unlink the the two.  Never mind the fact that on the diagram, the rendering clearly shows it's an Association Class, the menus don't.

THEN

you discover that the Association won't select consistently!

AND

since there isn't a means to unlink the Class from the Association from the <edge context menu>, you're left up the creek without the proverbial paddle!

This is EAUI of the purest form...  

Now lest my fellow users think I'm being too harsh... I'm NOT finding these wierd bugs by rigourously testing this product.  I'm just trying to use it to do my real job - Data Architecture!  (By the way I'm using IE notation on the diagram)

EA SERIOUSLY reduces my productivity over what it should be!

If there was anything better than EA out there I'd switch in an instant!  It is a sad indictment on our industry...  (You might gather I've had a tough time with EA this week - I actually started to use it again...)

Paolo
Using EA in spite of EA not because of it...  

Caveat - it may be that this is happening ONLY on my machine (hence the question at the start).  In which case I plead that the observed behaviour is only slightly stranger than the already admitted inconsistencies in EA!

[«Midnight»]

I've not yet had time to try this Paolo.

Today's a bust, but if you don't get feedback for another day get after me directly and I'll try it.

Could this be somehow related to the schizophrenic handling of aggregations (et al) you noticed when UML 2.x support first appeared in EA (and that persists still)?

David

[Paolo F Cantoni]

Could this be somehow related to the schizophrenic handling of aggregations (et al) you noticed when UML 2.x support first appeared in EA (and that persists still)?

David

I wouldn't have thought so, but NOTHING in EA would surprise me...

Paolo

[Paolo F Cantoni]

THEN

you discover that the Association won't select consistently!

Figured out how to consistently select an AssociationClass edge...

You won't be surprised that it's a case of EAUI!

Sometimes, you may observe that the Notelink edge that connects the AssociationClass AssocationClass to the AssociationClass Assocation (try sayng that after a few beers!).  Appears to "miss" the Assocation edge (by, as Maxwell Smart would say, "that much" - thumb and index finger held close together, but not touching).

That's the key!  What that means for you, the user, is that EA is lying to you about where the edge really is...  If you try to select the edge by clicking ON the edge as you see it on the screen - it won't select!  If you click the empty space the same distance and direction AWAY from the edge on the screen as indicated by the amount of Notelink overshoot; you'll select the edge!  If your edge is "in line" with the Notelink, move it around and you should see the Notelink "overshoot"!

In other words if you click where it is, you won't get it - if you click where it isn't you will!  EAUI!

Can anyone else confirm?

Yours in incredulity...
Paolo