| Jay,
 
 Yes, those parts are bugs I was hoping for some guidance on.
 
 For 8, neither Kasper or I could find the source code for or any documentation or discussion about the issue when we looked over the summer. It's easy to create a simple example that shows the issue, though. Essentially, somewhere the EMF data structures
 are checking whether or not an object is set to another list or variable specified in the EMF model and removing it from that position when it's put in another one. So when a Vertex is added to a Triangle it is removed from all other Triangles. I tried implementations
 with both a list of Vertices or three explicit Vertex class variables, getting the same result.
 
 My intuition is that this is because of persistence to XML. EMF doesn't want the same object to appear twice in the tree that gets written to the file, so they make sure it can only appear in one place. 
 
 I'll put in a bug for replacing the table with a NatTable.
 
 For 15, I double checked and may have been over-complicating this. I may just be able to set up the ICEGeometryPage as an ITabbedPropertiySheetContributer to the same ID. I'll try it out and apply the same thing to the ICEMeshPage(which currently has the
 same issue) if so.
 
 Robert
 
 From: eavp-dev-bounces@xxxxxxxxxxx <eavp-dev-bounces@xxxxxxxxxxx> on behalf of Jay Jay Billings <jayjaybillings@xxxxxxxxx>Sent: Thursday, September 08, 2016 6:43 AM
 To: eavp developer discussions
 Subject: Re: [eavp-dev] Geometry Properties View screenshots
   
Robert, Excellent work! Both 8 and 15 are confusing and signs like bugs. Could you explain them more please? In 8, I don't understand why EMF is causing such a restriction. Can you point to the code that causes the duplicity restriction? In 8, have you looked at using SWT.Virtual for the table or considered using a NatTable? Creating a table should only take as long as is needed to draw the few entries that are actually displayed. 15 eludes me completely. Could you provide more information on the problem here? Certainly the properties view doesn't care if something is an item or not. Jay |