Handling Modified Library Files

Dealing with Library Updates When Files Have Been Customised

If a user modifies an XJEase file that came from a library, XJDeveloper will continue to track it after it has been edited and will offer to update it if a future library release contains a new version of the file. This applies to user-defined libraries as well as XJTAG's library.

Declining an update for an additional code file that is used by several devices can cause problems. For example, consider the case where a user modifies version 5 of the Math.xje additional code file to add a new format function. Later, a new library is released that contains version 6 of Math.xje and a memory test device file that relies on the new version. If a project is created that contains the memory but the library update for the additional code file is declined, further work will be required to make the memory's test device file run.

Declining library updates in order to avoid having to redo modifications to a file should therefore only be done with caution.

• When files are updated, the previous versions are automatically copied into a Backup directory that will be created alongside the project file. That allows any manual modifications to be copied from the original file (if an XJEase file has been edited, it is identified by the suffix "(Modified)").

Dealing with Modified Library Files

Test device files will often share additional code files. For example, an I²C ADC and an I²C EEPROM are likely to use the same file to perform communication over the bus. If a user has modified that file to work with one particular ADC, for instance, and later categorises the EEPROM, a warning will be displayed that a modified file is in use.

The opportunity is offered to use the original library version instead, as shown in Figure 7 below.

• Choosing to use the original library file will overwrite the modifications and will therefore affect all other devices using the same file.

Figure 7: Warning of a Modified Additional Code File

Option	Action
To use unmodified library file	Insert a tick into the Update to Latest Version box and click Continue.
To use modified file	Ensure there is no tick in the Update to Latest Version box and click Continue. Click Yes at the Not all definitions will be updated. Do you want to continue? prompt.
To stop the categorisation and return to previous screen	Click Cancel.

If the original library file is not used, it is important to know that the XJEase file for the test device being categorised will run correctly with the modified additional code file.