Is there a recommended way of making a node linkable and still allowing it to move? I tried the following and getting some inconsistent behavior.
I don’t know why that would be behaving irregularly for you. It’s odd that it’s working at all, because NodePanel.Sizing defaults to “Fixed” but you haven’t specified any Width or Height for the Rectangle.
I suggest setting NodePanel.Sizing=“Auto”, so that the Rectangle surrounds whatever size the Image is. And I suggest adding a Margin to the Image, so that there is always a thin(?) red area of the Rectangle available for linking operations.
Sorry, I left out the width and height in the post, but the problem still remains even with auto size. I have further information on it. It seems like if I drop the node in the upper left hand corner of the link analysis diagram it behaves as you would expect. When you click on the rectangle, it draws links and when you click on the image, it moves the node. If I drag the node all the way to the bottom right hand corner and then try to click on it I get a strange result. It seems like the behavior points where the node expects to see clicks is offset. For example if I drag the node to the far right, I need to click to the right of the image to move the node. If I drag it to the bottom right of the diagram i need to click to the right of the node and past the bottom of the node. Any idea where I should start to look? I suspect I did something to cause this happen, but not sure what could have caused it. Could the diagram somehow be interpretting left mouse down clicks on the node a the wrong position? It’s as if the mouse thinks the node is in a different position than it appears on the screen.
What platform and version are you using?
What are all of the controls or panels that the Diagram is in?
Admittedly I’m stumped. We are using prism, but the diagram is in a regular old UserControl. The version is 126.96.36.199
Are you using GoSilverlight?
If so, try using version 1.1.9, or 1.2.2.
Otherwise I have no idea what might be causing the problem.
Going to 1.2.2 fixed the problem!