x2 0.27 comments about dual scrap frames and synchronization

[sgp]

Nikos, happy birthday x2!!
I like dual scrap frames. I followed your example in alpha.txt to synchronize two hierarchies. As far as usability, the first thing I missed was a folder tree view to the left of the dual scrap frames. Can it be added?
Then I flattened the two hierarchies and started wondering about equally named files in different folders. Is one file going to overwrite the other in the scrap frame?

Even though in alpha.txt you do say that "This deep-sync feature works well when the 2 hierarchies have identical structures", I'm not sure ready for prime time. Here's my test. I started with folder1 and all its subfolders (several MBs of data). I made a copy of folder1, say f\folder1. Then I deleted several subfolders from folder1. Then i Rdragged folder1 into the left scrap pane and f\folder1 into the right scrap pane. Now folder1's hierarcy is a subset of f\folder1's hierarcy. When I hit F9 I got many question marks. I didn't expect to see any question marks when comparing a subset of a hierarchy with the full set. Is it a bug or is design?

[nikos]

the tree isn't necessary since scrap frames are not browsable

if a whole folder is missing from one pane then x2 at present considers it "undecided" and marks it with a question mark. If however the folder structures are the same then everything will work fine

otherwise the new sync-copy command would have to create a folder before copy would begin. Although this is not impossible, scraps may have a mixture of "random" items as well as flatened hierarchies so i'm reluctant creating folders here and there

keep in mind that the deep synchronization feature works by matching folders after organizing them in a tree-like fashion (it's very complex). Then it takes each folder pair and performs a simple synchronization, as in a normal x2 frame