[ ] include connectors doesn’t work

[Paolo F Cantoni]

When pasting with [Ctrl+Shift+V] [ ] include connectors doesn’t work. Regardless of the checkbox setting, the connectors (if present) are always included!  lease rectify!

Reported,
Paolo

[Paolo F Cantoni]

When pasting with [Ctrl+Shift+V] [ ] include connectors doesn’t work. Regardless of the checkbox setting, the connectors (if present) are always included!  Please rectify!

Reported,
Paolo

Seems to have improved...  (although I don't recall being notified that it was a bug, and certainly not that it had been rectified!)

If this is unmarked (that is, I DON'T wish to include connectors - by definition, ANY connectors), we still find that Generalization connectors are copied regardless.

Anyone else confirm this?  It may have something to do with our setup so I'd like confirmation before I report a (now?) bug.

TIA,
Paolo

[MRrobot]

Hi Paolo,

I can confirm that the copied connectors will not be displayed - but they will be copied as well.

If you look under Properties > Related > Links of the copied elements all connections should be there.
It's strange that the sequence flows on my test diagram between activities are not displayed, but from an activity to the end event they are.

Regards Michael

[Paolo F Cantoni]

Hi Paolo,

I can confirm that the copied connectors will not be displayed - but they will be copied as well.

If you look under Properties > Related > Links of the copied elements all connections should be there.
It's strange that the sequence flows on my test diagram between activities are not displayed, but from an activity to the end event they are.

Regards Michael

Sorry Michael, don't understand what you're saying.  If I unmark the checkbox I expect NO connectors to be copied/cloned.  Since they're NOT present, they can't be visible.

Can you clarify?

Paolo

[Glassboy]

Sorry Michael, don't understand what you're saying.  If I unmark the checkbox I expect NO connectors to be copied/cloned.  Since they're NOT present, they can't be visible.

Half a bee, philosophically
Must, ipso facto, half not be
But half the bee has got to be
A vis-a-vis its entity, d'you see?

[Eve]

As you've found Generalizations (from the elements being copied) are not controlled by that option.

It is intentional and (you may say incorrectly) expected by other users.

The reason is something along the lines of, without copying them you don't have a copy of the original.

[Paolo F Cantoni]

As you've found Generalizations (from the elements being copied) are not controlled by that option.

It is intentional and (you may say incorrectly) expected by other users.

The reason is something along the lines of, without copying them you don't have a copy of the original.

(my emphasis).  "You might well think that; I couldn't possibly say that."

Further, to use the (Margaret) Thatcher interrogative - "name three". 

Can't argue with user expectations.

Just in case, others can't follow the use case I'm describing, we use the functionality to create non-copies, but similar elements quickly.  During a session, we create a "prototype", load it up with as much as we can and then make multiple new items from the prototype; NONE of which are direct copies of the prototype.  We'll have to use a slightly different process.

Paolo