My question is: does the GoBasicNode (or any of its inherited ancestors) have undocumented .X and .Y properties? It’s certainly possible I missed something, but I haven’t been able to see them.
I ask because I have a custom class derived from GoBasicNode in which I implement .X and .Y properties, which are populated from values in a database. When I then go to render my diagram, I follow these steps:
- Load data from the database, including populating the custom X and Y properties.
- Update the appearance of my derived node, including its size.
- Update the “Center” of my derived node based on the X/Y properties from the database.
- Plot the points on the GoView.
I’ve isolated the problem to a line in step #2, where the “Size” property is set.
// _FeatureType.Size is a short
this.Size = new SizeF((float)_FeatureType.Size,(float)_FeatureType.Size);
The code above somehow changes the custom “X” and “Y” properties for my derived node. Note that changing the order of steps #2 and #3 above does not help solve the problem, though the effect is much greater if #3 occurs before #2.
Before I go and change my database and custom code to rename my X and Y properties, I was hoping that someone could provide insight here.