Re: [feature request] tree iteration order option

[Kai Willadsen <kai willadsen gmail com>]

On 30 December 2013 23:37, Karl-Philipp Richter <krichter722 aol de> wrote:
> Hi together,
> Another feature request: Providing an option for the tree iteration
> order, i.e. depth first or breadth first. Currently the tree is built
> depth first which has the disadvantage that the tree can only be
> explored from one start point during its construction. I don't know
> whether this (exploring the tree during its construction) is a specified
> feature of meld, but it seems to work pretty well anyway. If we just
> assume it would be, the user might explore a subtree and find a
> directory in this subtree which he/she wants to copy to the other side,
> so that the comparison for this subtree can be aborted because trees
> will be identical after copying. In a depth first search larger subtrees
> are made available earlier so that the profit from the described
> mechanism can be increased.

I think the short answer to this is that this really isn't a supported
use. I'm not shocked that it works, but I really wouldn't like to
guarantee that any actions would necessarily work as expected until
the tree is fully loaded.

Either way, we have some assumptions built-in to the tree construction
that rely on us doing a depth-first search, so it's not possible to
change the iteration order easily anyway.

cheers,
Kai