An Overview of the Chromperfect File Editor Program

Introduction

The File Editor Program is one of the core utilities within Chromperfect and plays a central role in how users create, manage, and maintain the files used throughout the system. For new users in particular, understanding the File Editor is an important first step toward working confidently with Chromperfect. Watch our YouTube video for more information.

This article provides a detailed overview of the File Editor Program, explaining what it is used for, the types of files it supports, and how it fits into everyday Chromperfect workflows. The goal is not to dive into advanced configuration, but to help users understand the intent, layout, and basic operation of the File Editor before moving on to more specialised topics.

What Is the Chromperfect File Editor Program?

The File Editor Program allows users to create, open, edit, and print Chromperfect files. It acts as a central editing environment for many of the files that define how data is acquired, processed, and reported.

Unlike acquisition or analysis programs, the File Editor does not perform data collection or calculations itself. Instead, it provides the tools needed to prepare and maintain the files that those other programs rely on. Because of this, the File Editor is used across many different workflows and is often one of the first programs new users encounter.

File Types Supported by the File Editor

Chromperfect works with a variety of file types, each designed for a specific purpose. The File Editor Program supports the creation, editing, and printing of most of these file types.

The most commonly used file types include Method files, Calibration files, SEC Calibration files, and Format files. Method files define how an analysis is performed, including acquisition parameters, processing rules, and reporting options. Calibration and SEC Calibration files define how peaks are identified and quantified. Format files control how reports are laid out and presented.

The File Editor also supports Sequence files, which define a series of runs or processing steps, and Results Job files, which are used for managing processing tasks.

Several types of Instrument Setpoint files are supported as well. These files define the operating conditions that are sent to an instrument and are often referred to as instrument control files. Setpoint files are ancillary to Method files and describe how the instrument itself should be configured during a run.

Raw data files may be opened and viewed by the File Editor under certain conditions, although their creation is subject to user permissions. The File Editor may also use Bound files, but it cannot create them.

Together, these file types form the foundation of a Chromperfect system, and the File Editor provides a consistent way to work with them.

Multiple Document Interface

The File Editor Program uses a multiple document interface, often referred to as an MDI. This means that multiple files can be opened at the same time, each in its own editing window.

This design allows users to compare settings, copy information between files, or work on several related files without repeatedly opening and closing the program. For example, a user might have a Method file and a Format file open at the same time while making coordinated changes.

Only one editing window is active at any given moment, but switching between open files is straightforward using the mouse or the Window menu.

Launching the File Editor

The File Editor Program is launched from the Chromperfect Main Menu by selecting the Files option. When the program opens, the main window may appear empty if no file has been opened yet.

This behaviour is normal. The File Editor does not automatically load a file unless instructed to do so. Users explicitly choose when and what to open, which helps prevent unintended changes.

The File Menu

Most day-to-day actions in the File Editor are performed through the File menu. This menu provides access to creating new files, opening existing ones, saving changes, printing, and exiting the program.

Each of these actions follows consistent and predictable behaviour, making it easier for new users to learn the program.

Creating New Files

New files are created using the File → New command. When this option is selected, a dialog appears showing the different types of files that can be created.

Each button in this dialog corresponds to a specific file type. Selecting a file type creates a new file in memory and opens the appropriate editor form. At this stage, the file has not yet been written to disk.

Some file types require additional information during creation, and certain buttons may be unavailable depending on user permissions or file type restrictions. For example, most Instrument Setpoint files can only be created by uploading information from an instrument.

Opening Existing Files

Existing files are opened using the File → Open command. This presents a dialog similar to the New File dialog, allowing users to select the type of file they wish to open.

Once a file type is selected, a file inquiry dialog appears where the file name and location can be specified. After confirmation, the file opens in its own editing window.

Multiple files can be opened at the same time, and multiple selections are supported. If the same file is opened more than once, only the first instance is editable, while additional instances are opened in read-only mode.

Working with Multiple Open Files

When several files are open, each appears in its own editing form. The active form is highlighted, while inactive forms are dimmed.

Most menu actions apply only to the active form. Users can activate a different form by clicking within it or by selecting it from the Window menu.

This behaviour helps reduce the risk of making changes to the wrong file while still allowing efficient navigation between open files.

Saving Files

Changes to a file are saved using the File → Save command. This writes the current contents of the active editing form to disk and increments the file version number.

If a file has never been saved before, Save behaves like Save As and prompts the user to specify a file name and location. If a file is opened in read-only mode, saving is disabled unless a new file name is chosen.

The File → Save As command allows changes to be written to a different file. This is commonly used when creating a new Method based on an existing one, as it preserves the original file.

Closing Files and Exiting the Program

Files are closed using the File → Close command or by clicking the close control on the editing form. If changes have been made, the user is prompted to save or discard those changes.

Exiting the File Editor is handled through the File → Exit command. If multiple files have unsaved changes, the user is prompted for each one in turn. This ensures that no changes are lost unintentionally.

Printing Options

The File Editor provides several ways to print file contents. Files can be printed directly to a printer, previewed on screen with pagination, displayed on screen without pagination, or written to a text file.

Printing options vary depending on the file type, and graphical elements such as plots may be omitted when printing to text or screen-only formats.

These options are useful for documentation, review, and troubleshooting.

Edit, View, and Window Menus

The Edit menu provides standard Cut, Copy, and Paste functionality for working with text within editing forms. These operations also support common keyboard shortcuts.

The View menu controls the appearance of the File Editor window itself, including whether the toolbar and status bar are displayed. The status bar provides useful information about the active file, such as version number and last modification date.

The Window menu controls how open editing forms are arranged and allows quick navigation between them.

A Note on Solution Files

Chromperfect also supports Solution files as an alternative way of organising methods and their supporting files. A Solution file is a self-contained container that holds a Method together with its associated Calibration, Format, and other ancillary information, rather than referencing these files externally.

Solution files are edited using a separate program called the Chromperfect Solution File Editor, not the File Editor described in this article. Users typically choose to work either with Method files and external supporting files, or with Solution files, depending on their preferred workflow.

While both approaches can coexist on the same Chromperfect system, many users find it simpler to remain consistent and use one approach throughout.

Conclusion

The File Editor Program is a foundational part of Chromperfect and is essential for managing the files that define how analyses are performed.

By understanding the purpose of the File Editor, the types of files it supports, and how its core features work, new users can build confidence and avoid common mistakes early on. As users become more familiar with Chromperfect, the File Editor continues to serve as a reliable and consistent tool for maintaining and refining their workflows.

This article accompanies the Chromperfect training video on the File Editor Program and provides a written reference for users who prefer step-by-step explanations or want to revisit specific topics.