The behaviour of Synchronise It! changed when a new PKG-file is created since July. The new behaviour is correct, but it causes problems with the storage capacity of my USB-stick if the bases to Synchronise are too big. That was not a problem with the older versions of Synchronise It! and that is why I like the old behaviour better.
After one creates a session which a package as TARGET, and one gives the command 'Synchronise' in the preview window it starts packing all files missing on the target system in the PKG-file. In my case (working with big bases to compare) my USB gets out of storage capacity.
With the old behaviour Synchronise It! seemed to pack all files destined for the target system, but for some reason, these files never made it to the PKG file in the case that the PKG-file did not yet exist on the USB. Synchronise It! only listed the files of the SOURCE system.
I thought that older behaviour to be very useful, as in my case it worked very well (although it needed an extra step: listing on the one system, comparing on the other system). After creating the listing I would move the USB to the target PC, and there I could compare which that system with the listing stored in the package file.
I work with bases that are big, and files out of synch are only a small part of the total bases.
Could this behaviour be optional? Synchronise It! asks the user if the new package file should be created, if it does not yet exist. That could be the moment that the option could be offered to synchronise the new PKG, or only create a listing of the source system.
