  |
GoFiler Legato Script Reference
Legato v 1.6f Application v 6.4a
|
| Table of Contents | < < Previous | Next >> |
Chapter Sixteen — Application (continued)
16.4 Application Settings Overview
Scripts can store and read settings within INI style files and the Windows Registry. INI style settings can be stored as text or as encrypted text while registry settings are constrained by the data types supported by Windows.
As a matter of convention, scripts should store the majority of their settings within INI files, and, to the extent possible, in the users application area. This makes the settings unique to the user and also does not pollute or bloat the Windows Registry. Generally, the INI format is useful for private and local information while the registry tends to be used for more widely available data.
Application data is split into two files stored in the user data area: Settings and Preferences:
Application Settings are incidental data such as file history, application screen position etc, while preferences are parameters ranging from EDGAR data, default project information, conversion options, etc. Application setting are user and workstation centric.
Application Preferences include a wide swath of information ranging from formatting defaults such as spacing, data conversion options, viewing settings, specific product data such as EDGAR setting and so on. Application preferences also can be deployed on an enterprise basis. Application preferences are enterprise and work flow centric.
While application data is stored in INI file format, the application preferences are managed in a manner in which it is not safe to access the file directly. Separate high level API functions are provided for managing application preferences.
An important note as to terminology and legacy support: as the application evolved and grew, the need to maintain legacy support was paramount. Hence, the preferences are stored in the file with the suffix ‘settings’. For example, for GoFiler Complete, the application ‘preferences’ are stored in the file “GoFiler Complete Settings.ini” while the ‘settings’ are stored in the name “GoFiler Complete.ini”. The second name for settings is typical for Windows application.
There are three areas covered by settings:
Initialization File Settings — Typically known as INI files, they store setting and preference information in text form using section and parameter names. The INI settings API is considered low-level. While application preferences are stored in INI format, programmers should avoid directly reading and writing such settings.
Application Preferences — These are managed settings or preferences where each module within the application reads and writes its specific parameters on application open or when settings are changed by the user or a specific event.
Registry Settings — API functions are provided to access the system registry, While the Application does not generally employ the registry for normal operation, scripts may need to access the registry or even set or adjust entries.
Page revised 2026-01-05
| Table of Contents | < < Previous | Next >> |
© 2012-2025 Novaworks, LLC. All rights reserved worldwide. Unauthorized use, duplication or transmission is prohibited by law. Portions of the software are protected by US Patents 10,095,672, 10,706,221 and 11,210,456. Novaworks, GoFiler™ and Legato™ are registered trademarks of Novaworks, LLC. EDGAR® is a federally registered trademark of the U.S. Securities and Exchange Commission. Novaworks is not affiliated with or approved by the U.S. Securities and Exchange Commission. All other trademarks are the property of their respective owners. Use of the features specified in this language are subject to terms, conditions and limitations of the Software License Agreement.