This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
We are running into an issue where connection intersections are calculated even when DiagramSurface.CanCalculateConnectionIntersections is false. This is causing a memory leak in our application, because even after the DiagramSurface is unloaded, there is still a reference to it through the connections in the static Dictionary in ConnectionIntersectionCache. There is also a potential performance implication. Looking at the source, it appears that intersections are added to the cache in DiagramGrid.AddConnection and removed in DiagramGrid.RemoveConnection regardless of the state of the flag. DiagramGrid.UpdateConnectionBuckets respects the flag, but is the only method that does. Is this the intended behavior? Thanks, Brian Version: 4.0.289.23452 |
|
|
|
|
Hi Brian, Thanks for contacting us. I will be looking into this for you early next week. -Jason Fauchelle |
|
|
|
|
Hi Brian, Thanks again for pointing this out. This is not the expected behaviour, and so I've fixed this for the next nightly build. Everything that works with the connection intersection cache will now respect that flag. The next nightly build will be available after around 1200GMT which you'll be able to download from here: http://www.mindscapehq.com/products/wpfdiagrams/nightly-builds Let me know if you have further questions. -Jason Fauchelle |
|
|
|
