Agilent Technologies U9072A cdma-2000 Quick Save

190

System Functions

Quick Save

Quick Save

The Quick Save front-panel key repeats the most recent save that was performed from the Save menu,

with the following exceptions:

If the current measurement does not support the last non-register save that was performed, an

informational message is generated, “File type not supported for this measurement”

Quick Save repeats the last type of qualified save (that is, a save qualified by the above criteria) in the

last save directory by creating a unique filename using the Auto File Naming algorithm described below.

If Quick Save is pressed after startup and before any qualified Save has been performed, the Quick Save

function performs a Screen Image save using the current settings for Screen Image saves (current theme,

current directory), which then becomes the “last save” for the purpose of subsequent Quick Saves.

The Auto File Naming feature automatically generates a file name for use when saving a file. The

filename consists of a prefix and suffix separated by a dot, as is standard for the Windows® file system.

A default prefix exists for each of the available file types:

A four digit number is appended to the prefix to create a unique file name. The numbering sequence

starts at 0000 within each Mode for each file type and updates incrementally to 9999, then wraps to 0000

again. It remembers where it was through a Mode Preset and when leaving and returning to the Mode. It

is reset by Restore Misc Defaults and Restore System Defaults and subsequent running of the instrument

application. So, for example, the first auto file name generated for State files is State_0000.state. The

next is State_0001, and so forth.

One of the key features of Auto File Name is that we guarantee that the Auto File Name will never

conflict with an existing file.The algorithm looks for the next available number. If it gets to 9999, then it

looks for holes. If it find no holes, that is no more numbers are available, it gives an error.

For example, if when we get to State_0010.state there is already a State_0010.state file in the current

directory, it advances the counter to State_0011.state to ensure that no conflict will exist (and then it

verifies that State_0011.state also does not exist in the current directory and advances again if it does,