bug: components are always added back into all diagrams

mindplay · Post by **mindplay** » Fri 30 Dec 2011 19:41

In some views, a related entity may be relevant, but I don't want to include all of it's components, as they have no particular relevance in other views.

Removing components from a view works fine, but when you save the view, close and re-open it, all of the components are added back to it, appearing in random locations in the diagram.

Helen · Post by **Helen** » Wed 04 Jan 2012 09:27

Thank you for posting. We will fix the "adding components back into diagrams" issue.
We will post here when the corresponding build of Entity Developer is available for download.

Helen · Post by **Helen** » Thu 12 Jan 2012 15:06

We've fixed the problem with incorrect model diagram saving after deleting a complex type from a diagram.

This fix is available in the latest 4.2.110 build of Entity Developer. The new build can be downloaded from http://www.devart.com/entitydeveloper/download.html (the trial version) or from Registered Users' Area (for users with active subscription only).

For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=23135

mindplay · Post by **mindplay** » Tue 14 Feb 2012 17:20

This problem just surfaced again, in a slightly different way.

When I add a component property to an entity on one diagram, the same component (the actual complex type) shows up again on other diagrams where it was not visible.

Helen · Post by **Helen** » Mon 20 Feb 2012 12:52

Thank you for your report.
Unfortunately, we cannot reproduce the issue in our environment at the moment.

mindplay · Post by **mindplay** » Tue 21 Feb 2012 14:30

I can't reproduce this either - must have been a very edgy case. It hasn't happened again - but I'll try to track it if it does...

mindplay · Post by **mindplay** » Tue 21 Feb 2012 16:50

Oh, it just happened, and it is reproducible - simply drag an existing entity (that references some components) onto a second diagram, it adds all of that entity's components into the second diagram.

Helen · Post by **Helen** » Fri 24 Feb 2012 10:37

This behavior is by design.
When adding an entity with a property of a complex type or enum type to a diagram, we always create the corresponding complex type or enum on the diagram. It makes the model more evident and helps to understand the connections between different model objects.