Cleaning path/search space memory

[Shirkit]

This issue happens when you are using the tool on a scene and then load a new scene and try to play around with the tool. It crashes. Therefore we should clean the memory when loading a new level in the editor.

[Shirkit]

Indeed this needs to be changed. The easiest way I can think of solving this would be to re-instantiate the editor classes, but for that we need an event, and I searched for it on the past and couldn't find it.

Maybe we can solve this by on updates, check for http://docs.unity3d.com/Documentation/ScriptReference/EditorApplication-currentScene.html and fire an event on our own for the software.

I can solve the crash, but everything else will have unpredictable behavior if no event for that is fired. If no other solutions or ideas comes up, we can try to implement that one.

[TontonTremblay]

I think it will be possible to save the name of the level you are working on when the user presses "pre-compute maps". From there it is easy to check the current name vs. the name saved and then clean if they are differrent.

[Shirkit]

Can't be there since there will be more things going on before the user pressing Precompute. The WindowEditor will point to the wrong Drawer meanwhile, trying to access a MonoBehavior that will point to a GameObject that isn't on the screen, trying to draw things that doesn't exist. The Play animation will probably crash also. The check can't be there on pre-compute or it won't solve the problems.

[TontonTremblay]

So it needs to be a general statement at the beginning of the editor update that checks if the name of the level did not change. We can save the name of that level when we pre-compute. This should work?

[Shirkit]

Yes, exactly that. When the name changes, we'll be able to detect before throwing an exception and applying the necessary things to properly organize the things that needs to be organized.