Notes on Synchronization and Backward Compatibility

Previous Next

In previous versions of USoft Developer, the synchronization routine had to be started or restarted manually by the developer. Because synchronization in USoft Developer from version 5.0 onwards is automatic, the Synchronize option no longer exists.

Upgrading to 5.1 and 5.2 is fully transparent in this area. In spite of synchronization being automated, your painted application should be identical to the way you left it in the previous version.

Automatic synchronization is much faster because it no longer inserts records in your ESI repository. It does, however, require a slightly different way of working.

It is no longer possible to rename or delete classes created for you by the automatic synchronize routine.

· To change the name of an Info Window class, change the Object Name Plural as specified for the table in the Definer. The window class is automatically renamed next time you open the Windows Designer.


· To change the name of a Related or Lookup Window class, change the Related Window Name or Lookup Window Name as specified for the relationship in the Definer.


· To change the name of a subtype window, change the Object Name as specified for the table.

In previous versions of USoft Developer it was possible to revert to a default (non-painted) version of an info window by deleting the painted window class from the Windows Designer catalog and then manually re-synchronizing it. This way of working is no longer possible since USoft Developer 5.2, as you can no longer delete automatically synchronized window classes. However,

· To get a "clean", non-painted window class, you can always use the New Info Box option.


· If you create a subclass of an automatically synchronized window class before you start customizing it, you can always revert to the "clean" non-customized superclass.