Differences

This shows you the differences between the selected revisions of the page.

2025-01-28 2025-02-14
6.4.2 Issue 2318 – Optionally push synchronization actions to queue (martin) in background consistency (martin)
Line 48: Line 48:
Use //Commands// button to execute [[custom_command|custom command]] over pair of files (local and remote). Selection of custom commands is limited to those executed [[custom_command#types|both with local and remote files]] ("diff" commands). You have to select update action (blue arrow), i.e. where both local and remote file exists, to execute the custom command. Use //Commands// button to execute [[custom_command|custom command]] over pair of files (local and remote). Selection of custom commands is limited to those executed [[custom_command#types|both with local and remote files]] ("diff" commands). You have to select update action (blue arrow), i.e. where both local and remote file exists, to execute the custom command.
-===== [[background]] Starting on Background ===== +===== [[background]] Starting in Background ===== 
-By default, when clicking //OK// button, the synchronization proceeds in the foreground, blocking WinSCP window. Alternatively, you can select //Start on Background// in drop down menu of the //OK// button. That converts all synchronization action into [[transfer_queue|background operations]]. +By default, when clicking //OK// button, the synchronization proceeds in the foreground, blocking WinSCP window. Alternatively, you can select //Start in Background// in drop down menu of the //OK// button. That converts all synchronization action into [[transfer_queue|background operations]].
&beta_feature &beta_feature
Another option is to [[ui_synchronize#new_window|start synchronization in a new WinSCP window]] from the Synchronize dialog. Another option is to [[ui_synchronize#new_window|start synchronization in a new WinSCP window]] from the Synchronize dialog.

Last modified: by martin