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
|
Hello, we have problems with the A* pathfinder after loading a second view with a diagram. I looked in the code and found that the pathfinder holds a static dictionary with the diagram as key. Therefore the whole object hierachie remains in memory and all attached eventhandler fires on changes in the second instance. Kind regards Markus |
|
|
Hello Markus I will be looking into a solution for this tomorrow. Jason Fauchelle |
|
|
Hello Markus I was unable to reproduce the key not found exception. Steps to reproduce this will help to look into this. At the moment the A* pathfinder need to be coupled to the diagram in order to function. The memory issue (and probably also the exception issue) can be avoided if you use a different AStarPathfinder instance for each diagram model. Jason Fauchelle |
|
|
Hi Jason, sorry for the late replay. I was on a vacation for a few days. Creating separate instances isn't a solution because the dictionary inside the pathfinder is static. What worked for me is clearing the dictionary via reflection. I can't send you the production code, so i tried to isolate the problem in a sample, but i can't reproduce it ! So maybe it is something in our code. i need more time to find this out. Thank's Markus |
|