Strange layout of components

[asl]

Hmm ok. Well this has for some reason put every component in one row, which doesn't seem very space efficient

Compare this to the original packing method:

Originally posted by @rlorigro in #91 (comment)

[asl]

Ok, apparently the shiny new TileToRowCCPacker from OGDF was doing some strange things in some cases. So, I went ahead and ported old "embedded" packer which seems to work better and has some useful features.

I'm having the following packing of components which look reasonable to me given the aspect ratio

[rlorigro]

That looks reasonable to me as well. The old version used to sort them by size, which was nice in some ways, but I don't have a strong preference.

[asl]

That looks reasonable to me as well. The old version used to sort them by size, which was nice in some ways, but I don't have a strong preference.

This is the old version :) Note that the layout depends on aspect ratio. Essentially it tries to organize components in row-column fashion trying to preserve the aspect ratio. The algorithm is greedy: it tries to place the new component in any empty spot in every "row". And if there is no space – new row is added. As a result, if we're having one large (and wide) component, then everything got organized by size with the default square aspect ratio.

For the record, here is the layout with square scene (upper one was more rectangular):

[rlorigro]

Oh ok interesting. I didn't expect aspect ratio to make all the difference. I assumed the threading is what reordered things. Thanks

[asl]

Oh, no. The components are always processed being sorted by height (and first optionally rotated to be more "horizontal"). So, yes, sometimes small components could fit into spare spot