application_options_dialog.htm
Table of Contents
(Located in the IDE Tools Menu)
gen3 synchronizationgen3 generationgen3 registrygen3 application
gen3gen3gen3 editor
The Application Options dialog allows you to specify default settings for each new application you create.
Application tab
Require Dictionary | This option specifies that each new application must have a data dictionary. |
Default Dictionary | Names a data dictionary file as the default which appears in each new Application Properties Dialog . You can change to another dictionary before closing the dialog. |
Display Repeated Functions | Check this box to have the Application Generator (Procedure tab only) provide full expansion of procedures called from more than one place in the Application Tree. Clear the box to provide full expansion of only the first instance–every other instance is marked “Expanded Above.” |
Procedures per Module | The Procedures per Module spin control specifies the number of procedures that the Application Generator writes to each source code module. This can affect compile time when used with Conditional Generation turned on. Specifying one procedure per module, for example, means that each successive compile rebuilds only those procedures changed since the last one, and no more. The down side to this is that it requires more disk space. When using the ABC templates, we recommend 10-20 procedures per module. |
Application Wizard | Check this box to specify the default when creating a new application is to use the Application Wizard. You can override this choice when creating an application by checking or unchecking the Application Wizard box in the Application Properties dialog. |
Procedure Wizards | Check this box to specify the default when creating a new procedure is to use the appropriate Procedure Wizard. You can override this choice when creating a procedure by checking or unchecking the Procedure Wizard box in the Select Procedure Type dialog. |
Auto-save APP if recovery file's size exceeds the limit. | Use the spin box to set in MB the file size limit of the application recovery file. Maximum size before auto-save is 1000MB. |
====== IDE tab ======Open Dictionary Files and Template Registry as Read-Only | Specifies file management options for multiple developer projects. When checked, Dictionary files and the registry are opened read-only. |
Translate controls to control templates when populating | Check this box to have the Window Designer prompt you with a list of appropriate control templates whenever you place a control. We recommend this setting for new Clarion users. |
Import name clash action | Specifies how the Application Generator handles procedure names from an imported application file that clash with procedure names already resident. Choose from the following: |
Query on first clash | When the first clash is encountered, the Application Generator prompts for specific instructions on how to handle this clash and each subsequent clash. Choose from Auto Rename, Replace All, or Prompt. |
Auto Rename | Renames all imported procedures with name clashes by appending a sequence number to the imported procedure name. |
Replace All | Replaces all resident procedures with imported procedures of the same name. |
Prompt | Asks for specific instructions for each clash encountered. Choose from Replace or Rename. |
Replace | Replaces the resident procedure with the imported procedure of the same name. |
Rename | Prompts you to rename the imported procedure. |
Ask for alternative | For all procedures with the same name, the Application Generator prompts you to rename each imported procedure. |
Auto Rename | For all procedures with the same name, the Application Generator renames the imported procedure by appending a sequence number to the name. |
Replace previous | For all procedures with the same name, the Application Generator replaces the resident procedures with the imported procedures. |
Disable Column Prompts | Specifies that template-generated field-specific prompts will not display. This does not disable prompts created by Control Templates. |
Sort Embeds Alphabetically | Check this box to show embed points in alphabetical order in the Embedded Source dialog. Clear the box to show the embed points in “logical” order (order of execution). See Embedded Source Code for more information. |
Action for Legacy embeds | Specify how the Application Generator handles legacy embed points. Legacy embed points are generally provided for backward compatibility among template chains. They allow newer template chains to conditionally support embed points from older template chains. See LEGACY in the Template Guide. Choose from: |
Ignore all | Application Generator neither displays Legacy embed points at design time nor generates any code embedded therein. We recommend this setting to reduce “clutter” when developing new applications. |
Show all and generate | Application Generator displays all Legacy embed points at design time and generates any code embedded therein. We generally do not recommend this setting; however, it can be useful for developers that are very comfortable with a particular template chain and its embed points. |
Show filled and generate | Application Generator displays only filled Legacy embed points at design time and generates any code embedded therein. We recommend this setting for applications ported to a new template chain. |
Edit embedded source errors in generated code | Check this box to allow you to edit embedded source errors in the generated source code instead of the standard Embeditor. The advantage of this is a logical view of all source code as generated. You can edit the source error and the application generator will not regenerate code until after the Make and Run is completed. This is useful during the testing phase of your development for faster prototyping. |
Auto-Make Applications before compile | Check this box to trigger the Application Generator to generate source prior to the Build action if needed. |
Auto start designer on pressing the Window or Report button. | Check this box to auto-load the target Designer when pressing the Window or Report button located on the Procedure Properties window. You can still view the Window or Report text by pressing the tabs in the Procedure Properties window. Closing the Designer will direct you to the appropriate Window or Report tab. |
Move the MASK attribute from windows to controls | Check this box to allow the application convertor to automatically move the WINDOW MASK attribute to target ENTRY controls. If you plan to build the application in any version prior to 7, leave this check box blank. |
Registry tab
Template Language code can be logically split among many files. Clarion uses the files to produce one logical template set for creating applications. The Registry Options are mainly for programmers who produce their own template files or make modifications to the default templates.
Re-register When changed | To automatically re-register your templates when the Application Generator detects a change, check the Re-register When changed box. This defaults to “On.” |
Update Template Chain when edited | To automatically update the Template files when making a change in the Template Registry, check the Update Template Chain when edited box. |
Regenerate Deleted Templates | To specify the Application Generator should re-generate the .TPL and .TPW files from TemplateRegistry.TRF, should the files be deleted, check the Regenerate Deleted Templates box. |
#APPLICATION template | Select the default APPLICATION template from the drop-down list. The APPLICATION template controls source code generation. See Template Overview in the Template Guide for more information. |
Generation tab
Enable #ASSERT checking | Check this box to enforce heightened error checking during source code generation. This allows the Application Generator to identify certain template execution problems and notify you during source code generation. This slows the code generation process slightly. Clear the box for faster, but riskier source code generation. See #ASSERT for more information. | |
Use long file names for generated files | The default generation of application source files is the full application name followed by a three digit module number. If you would like to use the older 8.2 naming format, uncheck this box. | |
Use dot syntax for fields of structures | Used for the Clarion.NET Application Generator to generate field qualification syntax for all data structures instead of the older prefix:label format. | |
Lock Retries | Files required during code generation can be locked temporarily by automatic backup programs, anti-virus software, and other programs. This setting specifies how many times the IDE will attempt to gain access to the file before reporting an error. | |
Sort %File the same as the Dictionary Editor | %FILE template symbol returns files in the same order that they are displayed in the dictionary editor.Note: This means FILEs are generated in this order |
| Create local maps | Check this box to generate a MAP structure for each source module that prototypes only the procedures referenced in the module. This results in faster compiles whenever you add new procedures or change procedure prototypes, because only the affected modules are recompiled. To generate accurate local maps, you must use the Procedures button in the Procedure Properties dialog to identify any procedures referenced in embedded source code.Clear this box to generate a single MAP for the PROGRAM module that prototypes all the program's procedures globally. This results in slower compile times whenever you add new procedures or change procedure prototypes, because the change to the PROGRAM module forces a recompile of all application source modules. (Valid only for ABC template chain) |
| Enable embed commenting | Check this box to optimize automatic comment generation specified by the application templates. |
====== ======
====== Synchronization tab ======
This tab lets you specify how and when control attributes defined in your data dictionary are applied to your application's procedures and controls. See Also: How to Synchronize your App and Dictionary .
| Synchronize Application when opened | Check this box to reapply data dictionary attributes each time your application is opened. Clear the box to apply the attributes only on your explicit command. |
| Synchronize Window definitions | Check this box to apply data dictionary attributes to WINDOW structures during application-wide synchronization. Clear the box to ignore WINDOW structures. |
| Synchronize Report definitions | Check this box to apply data dictionary attributes to REPORT structures during application-wide synchronization. Clear the box to ignore REPORT structures. |
| Update controls for variables | Check this box to apply memory variable control attributes to their associated controls. Clear the box to ignore controls associated with memory variables. |
| Primary attributes only | Check this box to apply only the primary control attributes. Primary attributes are those attributes set directly in the Column Properties dialog. They include Column Name, Characters (length), Screen Picture, Prompt Text, Column Heading, Case (UPR, CAP), Typing Mode (INS, OVER), Flags (IMM, PASSWORD, READONLY), Justification, Initial Value, Help IDs, Messages, Tool Tips, and Validity Checks. Secondary attributes are those attributes set by pressing the Properties button on the Window and Report tabs of the Field Properties dialog.![]() ![]() ![]() ![]() | Press this button to reset the font and font size back to default settings. |
application_options_dialog.htm.txt · Last modified: 2021/04/15 15:56 by 127.0.0.1