Virtualized Connector End - Shape can't be selected

[Paolo F Cantoni]

If you “Hide a Relationship” on a Virtualized Connector End, it leaves the shape behind.  But that shape can't be selected and moved if the connector is hidden.  Unhide the connector and the shape can be selected.

Given that the centroid of the doppelganger appears to be located at the first way-point (as per the help), then you should be still able to select the doppelganger and move it - whether the line is visible or not.  Since in moving one, you are moving the other.

Reported,
Paolo

[Geert Bellekens]

In general the "virtualized connectors" are a weird animal.

I tend to advise against using them.

Geert

[Paolo F Cantoni]

In general the "virtualized connectors" are a weird animal.

I tend to advise against using them.

Geert

Yes,  I've tried to avoid them "like the plague" - even before the bugs I've reported.  But I need to create a viewpoint for senior managers that requires that the same element be shown multiply and separately on the same diagram (usually without the relationships showing - hence some of the other bugs reported).  So I have to use them.

Don't get me wrong, the problem of doppelgangers on a diagram is not an easy problem to solve, but this one is sub-optimal.  The requirement that only one connector per shape, however, is a good one and (if they fixed things up) would provide what most would need - for the present.

Paolo

[Eve]

If you don't need the relationships showing, another option is to drop a diagram frame and hide the frame. (Context menu | Appearance | Diagram Frame Appearance)

[Paolo F Cantoni]

If you don't need the relationships showing, another option is to drop a diagram frame and hide the frame. (Context menu | Appearance | Diagram Frame Appearance)

Thanks for that Simon,  At a pinch, it might do, BUT you do lose the ability to select and open the master from the doppelganger don't you?  Also, programatically you can't trace back to master - which I presume you can from the doppelganger t_diagramobject.

Each viewpoint isn't just communicating to the viewer, but represents metadata about the underlying model.

Paolo