2002 - ispLEVER: Why does the I/O vector editor in the Device Information window "Expand Option" not generate the I/O vector file (*.iov file) when user clicks “Apply” instead of “Save As"?
This is applicable to only "Custom" and "Dynamic" modes of the I/O State option in the Expanded window of Device Information GUI. By clicking “Apply”, the changes in the I/O states are made, but these changes are stored in the .XCF file. These changes are reflected when the device configures. The disadvantage in this option is that user need to change the IO settings again in a different configuration setup, as that would require a different *.XCF file. Changing IO settings for a custom environment can be time consuming for device with high pin count. However, saving an I/O vector file (by clicking “Save As”) helps user to re-use the same I/O states for a particular device, but with different setup or a different .XCF file. That prevents user from changing IO settings every time user change configuration set-up(resulting in a change in *.XCF file).