BARfly Help

BARfly Help - Options Menu - Data file save settings

Data file save settings

Select Options.Data File Save Settings to bring up the dialog box to the left. From this dialog, you can modify how BARfly saves data files.

A data file can be saved in more than one format. The settings in this dialog apply to all different possible formats for saving data: binary format, USS (universal state save), and the text dump formats.

The Preferred Save Format combo box selects between binary format, USS, UTD, and XML. When you select File.Save File, a data file is automatically saved in this format. When you select File.Save File As, the preferred save format is the option initially selected in the File Type combo box in the save dialog (you can still change the format).

Default tab stop in dump: For implementation files that lack a TABSTOP control variable definition, the length of each tab for generated text dumps is assumed to be this default number of characters long. This setting applies to the UTD and XML text dump save formats.
Use TABSTOP in dump: If the control variable TABSTOP is defined in an I.F., the length of each tab for generated text dumps is assumed to be this number of characters long. If the setting is unchecked, the default tab stop will always be used, even if TABSTOP is defined in an I.F. This setting applies to the UTD and XML text dump save formats.
Ignore Pause Points: Prevent incremental serialization from occurring. This forces the entirety of each file to be saved at once to the disk; there will never be any need to continually press F5 to continue serialization.
No Truncation: By default, BARfly destroys the previous contents of a file on the disk, if it existed, before trying to save over it. With this box checked, BARfly will not truncate the existing file. Instead, the contents of the file are overwritten starting from the first existing byte of the file. If any portion of the existing file on the disk is not overwritten, it remains as it was before the save operation. This is often a good way to update database-oriented formats, which might entail only incremental "record updates" instead of a complete rewrite of the entire file.
Revalidate before saving: You can automate the execution of the Run.Revalidate menu item as part of the save process. If the revalidation passes, the file is saved. If the revalidation fails, the file is not saved.