Suggestion: Reordering imports of trees about legendaryexplorer HOT 2 CLOSED

Part of this issue should be resolved in the final 3.0.9 as I now attempt local lookup of exports as parents. However I am not yet satisfied with how I do cross imports on top level packages. For example if you move a wwise tree to a new file that already has the same wwise package (as they may not have the same children) it may attempt to set import links to the original package.

I plan on making the level of the initial drop check to see if there are other items with the same name, and prompting the user if they want to merge into that instead or create a new export.

from legendaryexplorer.

This has been implemented, but needs checked. Merging trees is difficult as it is hard to tell item differences if the names are the same. It may be this feature will be restricted in this build until we have a more robust solution.

from legendaryexplorer.