• The "Project" tab, which allows you to enter general information about the project.
• The "Analysis" tab, which lets you associate one or more analyses with the project and/or a UML model.
• The "Data files" tab, which lets you enter information about the data files managed by the application (only available if the project is linked to at least one analysis).
• The "Live Data" tab, which allows you to configure how the data from the data files is displayed in the different editors.
• The "Languages" tab, which is used to configure the different languages used by the project as well as the options to be used for each language.
• The "Style" tab, which allows you to customize the print preview and to choose the skin template and custom style sheet. You can also configure screen sizes.
• The "SCM" tab, which is used to manage teamwork (SCM or Git).
• The "Options" tab, which allows you to define the creation, update and save options of the different elements of the project. This tab also allows you to synchronize templates, enable strict mode and define the code style.
• The "Advanced" tab, which allows you to enable "Reports and Queries", configure the AAFs and lock the application.
• The "Compilation" tab, which allows you to configure the compilation options.
• The "Telemetry" tab, which allows you to configure the telemetry options for the project.
  

General options

• Recompilar proyecto antes de generar las aplicaciones, bibliotecas, componentes, etc.:
  This option is used to force the project recompilation before each major operation on the project. This option is recommended for a multiple generation from a project.
  This option is also available in all wizards used to perform a deployment operation (executable creation, library creation, multiple generation, etc.)..
  Note: The application's compiled code directory is created in an "<Nom_Projet>.cpl" subdirectory of the compilation directory.. This compiled code directory contains the compiled code files for each element of the project: windows, reports, queries, etc.

UI errors

Compiler options

• Compilation error on unknown identifiers
  Defines whether a compiler error is displayed when the compiler encounters an unknown identifier (window name, field name, etc.).
• Compilation error on the off-configuration elements
  When this option is enabled, a compilation error occurs when it is used in the code linked to a configuration of elements outside configuration. The <COMPILE IF> statement is used to manage the code compilation according to the platforms and to the configuration types.
• Scope of local variables limited to the current block
  If this option is selected, the local variables will be specific to the block.
  You cannot use a local variable outside the block in which it is declared.
  The ending of the variable is run at the end of the block (destructors and freeing memory).
  You have the ability to redeclare a variable with the same name in two distinct sub-blocks but you cannot redeclare a variable with the same name in a child sub-block.
  If this option is enabled, the declaration of internal procedures using "range-limited" variables will result in a generation error.. Example:
  • the following code causes a compilation error:
    

    PROCEDURE MyProcedure()
    IF MyCondition THEN
        str is TO string // str exists only within the scope of the SI statement 
        INTERNAL PROCEDURE my_proc_interne()
            str = "thing" // -> Will cause an error in Java/Android generation
        END
    END

  • To correct this code, it is necessary not to declare the variable in the IF statement:
    

    PROCEDURE MyProcedure()
    str is TO string 
    IF MyCondition THEN
        INTERNAL PROCEDURE my_proc_interne()
            str = "thing"
        END
    END

  In Java and Android, we recommend always declaring internal procedures in the scope of the procedure itself.. Thus, if undeclared variables are used, compilation errors will be displayed.
• Allow "[% %]" in channels:
  This option allows the direct input of a variable name in a character string (also called "dynamic string construction"). To do so, use the following syntax:
  
  [%VariableName%]
  For example:
  

  // Ask for customer confirmation
  IF YesNo(Yes, "Do you confirm the creation of customer [%sCustomerName%]") = No THEN
  	RETURN
  END

  Caution: Using this option may mean modifying the code for certain WLanguage functions that already use the "[% %]" characters in their parameters. In this case, to avoid interpreting the "[% %]" characters, they must be preceded by "-%". Example:
  

  grTooltip(GR_Deadline, grTooltipFormat, "[%CATEGORY%]" + CR + CR+ "[%VALUE%]" + " H")

  becomes

  grTooltip(GR_Deadline, grTooltipFormat, -%"[%CATEGORY%]" + CR + CR + -%"[%VALUE%]" + " H")

  For more details, see String interpolation.
• Allow nullable types:
  Enables nullable types in a WINDEV, WEBDEV or WINDEV Mobile project. Allowing nullable types in a project changes the way your project handles null values. For more details, see NULL values: Allowing nullable types.
• Classes: ":" and "::" prefixes for access to optional members and methods
  Until version 14, the accesses to the members had to be performed by using the ":" and "::" prefixes. If this option is checked, these prefixes will not be required anymore.
• Classes: methods with the same name are automatically virtual.
  The methods with the same name in derived classes are automatically virtual.
  The "semi-virtual" mode kept for backward compatibility with WINDEV 4 and 5 is no longer available.
  The "virtual" keyword has no effect. No warning occurs on the virtual methods if the "virtual" keyword is missing.
• Arrays: deep copy
  This option makes arrays local by default. This means that the '=' operator performs a deep copy of the values in the array.
  If necessary, you can use the "dynamic" keyword so that the arrays point to the same reference.
• Arrays: protected access to elements passed as parameters to a procedure
  This option is used to protect an array element passed to a procedure as a parameter. This allows you to modify, delete or add elements into the array from this procedure.
  Note: When enabled, this option may slow down access to the array.
• Optimization: Activate inline extension:
  This option speeds up the execution of the application code. Whenever possible, the compiler automatically replaces the procedure call with its code. This may result in an overall increase in code size, but faster procedure calls.
• Optimization: optimized evaluation of Boolean expressions (AND, OR, IN):
  This option modifies the historical behavior of Boolean expressions:
  • If this option is checked, logical operators will operate in an optimized way by default: If the first part of the expression determines, the second part is not evaluated. This option is checked by default in new projects from version 2024 onwards.
  • If this option is unchecked, historical operation is retained: all elements of the expression are evaluated. To obtain optimized behavior, it is necessary to use the _ET_, _OR_, _WITHIN_ operators..
  For more details, see Logical operators.
• "Data source names":
  • "Variable name":
    "Data source" variables create a data source that use the name of the variable. This may cause a problem in the following cases:
    • using arrays of data sources
    • using data sources as class members.
    • when two windows use the same Data Source variable.
  • "Automatic name":
    "Data Source" variables use a unique name for the data source. Please note quotation marks must be removed to manipulate the data source. Don't write:
    
    M1 is Data Source
    HReadFirst("M1")
    but
    M1 is Data Source
    HReadFirst(M1)
  • "Automatic name with references":
    "Data Source" variables use a unique name for the data source. It is now possible to reference an existing data source, for example using the following syntax:
    
    x is Data Source
    x = FileName
    x = QueryName
    The NULL value is supported.
    

These compilation options are taken into account in Java and Android.