Home   Contacts   Links ZSKSoft Synchronizer documentation
  ZSKSoft Synchronizer  
  Demo examples  
  Terms of use  
  News subscription  
  Synchronization stages  
  Main window  
  My Synchronizations  
  Synchronization scheme  
  Creating, Opening, and Saving  
  Points types  
  Simple folder  
  ZIP file  
  FTP folder  
  Remote folder  
  Set as Source  
  Compare Contents  
  Additional commands  
Mark as Synchronized  
  Copy State  
  Reset state  
  Clock forward/backward  
  Program properties  
  Command line  
  Usage examples  
  Comparing versions  
  Synchronizing with laptop computer  
  Updating Web-site by FTP  
  Remote (offline) synchronization  
  License agreement  

Mark as Synchronized

By this command, ZSync saves current state in all points and considers them all synchronized between one another - even if they are actually radically different.

The command is available on the main menu (Commands/ More/ Mark as Synchronized) or on the object's context menu. When you launch this command, the following dialog will appear:

ForceOk.gif (15682 bytes)

The switch lets you choose which objects are to be processed: only those that match the current filter (taking into account the categories and gravity) or all.


Suppose, you need to use ZSync for managing a project that has been developing for a long time and is actually synchronized in general - however, some points have become surrounded with a great number of additional files and folders, which you don't have time to deal with. By selecting the Mark as Synchronized command, you will lock in the project state, and from this moment on ZSync will keep track of the new changes. If you later want to put some subfolders in order, at any time you can use the Compare actual state command.

Another example: imagine, the project being synchronized includes a configuration file, which is configured individually for a particular computer (e.g., it may contain paths to some folders, etc.) Therefore, this file must be among those that are synchronized (changes in this file must be transmitted to another computer), and at the same time it should not loose its identity, i.e. it cannot just be copied to another point.

These files should be treated as follows. Having made sure that they are properly configured on the both computers, use the context menu and run the Mark as Synchronized command. As a result, despite the obvious difference, ZSync will disregard them until one of them changes again. When that happens, you will see the file in the list of changed and scheduled for synchronization (by the way, to prevent possible overwriting of the entire file, you can berth (park) the file.) Now, manually enter the changes to the second file, and after that, again, run the Mark as synchronized command.

Of course, it would be much more pleasant if ZSync automatically "guessed" what exactly must be changed in the second file, but this job is quite delicate. Possibly, some time in the future versions this functionality will be provided; meanwhile, it can only promptly warn you that the file has changed, and you must also change the files in the other points. Nevertheless, this is already good enough.

  © ZSKSoft Lab 2001-2005   Designed by Vibe