PC SOFT

ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Home | Sign in | English EN

  • Overview
  • Compilation tab
  • General options
  • UI errors
  • Multi-configuration compilation
  • Programming standard
  • Compilation options
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
The project description window allows you to configure various elements of your project. This window includes the following tabs:
  • The "Project" tab, which allows you to enter general information about the project
  • The "Analysis" tab, which is used to associate an analysis with the project and/or with a UML model
  • The "Files" tab, which allows you to enter information about the data files used by the application (only if the project is bound to an 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 theme and the custom style sheet. You can also configure screen sizes.
  • The "Group" tab, which is used to manage teamwork (developer groupware or SCM).
  • The "Options" tab, which allows you to configure the template update, backup and synchronization options. This tab is also used to enable the strict mode and to define the code style.
  • The "Advanced" tab, which allows you to configure how to use "Reports & Queries", AAFs and how to lock the application.
  • The "Compilation" tab, which allows you to configure the compilation options.
  • Versions 22 and later
    The "Telemetry" tab, which allows you to configure the telemetry options for the project.
    WEBDEV - Server code This option is not available.
    New in version 22
    The "Telemetry" tab, which allows you to configure the telemetry options for the project.
    WEBDEV - Server code This option is not available.
    The "Telemetry" tab, which allows you to configure the telemetry options for the project.
    WEBDEV - Server code This option is not available.
Compilation tab

General options

The general options are as follows:
  • Compilation Directory: The directory of compiled code is created in a "<Project_Name>.cpl" subdirectory of compilation directory. This directory of compiled codes contains:
    • The files of compiled codes for each project element: windows, reports, queries, etc.
    • A subdirectory for each developer taking part in the project. This directory corresponds to the developer name. For more details, see Sharing the development of a project.
      By default, the compilation directory corresponds to the project directory. All your projects can be compiled in the same directory: to do so, specify the same compilation directory for all your projects.
  • Recompile project before generating applications, libraries, components, 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 the wizards used to perform a deployment operation (executable creation, library creation, multiple generation, etc.).
  • WEBDEV - Server code Display the compilation errors specific to Linux system: Used to specify that the project will be deployed in Linux. The compilation errors specific to a use in Linux are displayed.
  • Versions 20 and later
    WEBDEV - Server code Display compilation errors specific to pre-launched sessions: If your project uses pre-launched sessions, some functions can no longer be used when initializing the project. This option is used to identify the possible problems when using cached sessions. For more details, see Pre-launched sessions.
    New in version 20
    WEBDEV - Server code Display compilation errors specific to pre-launched sessions: If your project uses pre-launched sessions, some functions can no longer be used when initializing the project. This option is used to identify the possible problems when using cached sessions. For more details, see Pre-launched sessions.
    WEBDEV - Server code Display compilation errors specific to pre-launched sessions: If your project uses pre-launched sessions, some functions can no longer be used when initializing the project. This option is used to identify the possible problems when using cached sessions. For more details, see Pre-launched sessions.
  • Recompiling the project in order to synchronize the UI and the code:
    A recompilation is often required in order for the interface to be consistent with the code, for example when the name of an element was modified, the code of an element was modified, ... You can:
    • always propose to recompilation: a message is displayed, asking the developer whether the compilation must be performed. The compilation can be delayed in order to be performed later.
    • always perform the compilation without asking. If this option is checked, the recompilation may provoke slowdowns.
  • Versions 22 and later
    WEBDEV - Server code WLanguage browser: Allows you to choose the browser framework used for the project. From version 22, WEBDEV proposes a new WLanguage framework for the browser code. This new version proposes a behavior close to server code and it completes the features of browser code.
    Important: to use the new WLanguage framework, the generation standard of pages must be defined in "HTML 5".
    New in version 22
    WEBDEV - Server code WLanguage browser: Allows you to choose the browser framework used for the project. From version 22, WEBDEV proposes a new WLanguage framework for the browser code. This new version proposes a behavior close to server code and it completes the features of browser code.
    Important: to use the new WLanguage framework, the generation standard of pages must be defined in "HTML 5".
    WEBDEV - Server code WLanguage browser: Allows you to choose the browser framework used for the project. From version 22, WEBDEV proposes a new WLanguage framework for the browser code. This new version proposes a behavior close to server code and it completes the features of browser code.
    Important: to use the new WLanguage framework, the generation standard of pages must be defined in "HTML 5".

UI errors

UI compilation errors indicate the possible problems detected in your interfaces whenever a window, a page or a report is saved or whenever the project is recompiled.
By default, UI compilation errors are enabled for each new project created ("Enable UI compilation" checked).
Versions 22 and later
The "Edit the languages" button allows you to choose the project languages that will be taken into account by the UI compilation.
New in version 22
The "Edit the languages" button allows you to choose the project languages that will be taken into account by the UI compilation.
The "Edit the languages" button allows you to choose the project languages that will be taken into account by the UI compilation.
For more details, see UI compilation errors.
Versions 22 and later

Multi-configuration compilation

If the "Enable multi-configuration compilation (per user)" option is checked, all the project configurations will be compiled.
Therefore, the possible compilation errors in a given configuration appear immediately.
This option is very useful for a WINDEV Mobile project available in Android and iPhone/iPad for example.
Reminder: the project is compiled at each line break in the code editor, at each backup (Ctrl + S), ...
New in version 22

Multi-configuration compilation

If the "Enable multi-configuration compilation (per user)" option is checked, all the project configurations will be compiled.
Therefore, the possible compilation errors in a given configuration appear immediately.
This option is very useful for a WINDEV Mobile project available in Android and iPhone/iPad for example.
Reminder: the project is compiled at each line break in the code editor, at each backup (Ctrl + S), ...

Multi-configuration compilation

If the "Enable multi-configuration compilation (per user)" option is checked, all the project configurations will be compiled.
Therefore, the possible compilation errors in a given configuration appear immediately.
This option is very useful for a WINDEV Mobile project available in Android and iPhone/iPad for example.
Reminder: the project is compiled at each line break in the code editor, at each backup (Ctrl + S), ...
Versions 23 and later

Programming standard

These options are used to define a programming standard. The programming standard "errors" signal the code lines that do not respect this standard. These errors are displayed in the "Compilation errors" pane.
The available options are:
  • Versions 26 and later
    Standard or prefix syntax: This option allows or disallows the use of standard and prefix syntax.. You can allow both, only standard or only prefix syntax (e.g., "ListControl.Add").
    New in version 26
    Standard or prefix syntax: This option allows or disallows the use of standard and prefix syntax.. You can allow both, only standard or only prefix syntax (e.g., "ListControl.Add").
    Standard or prefix syntax: This option allows or disallows the use of standard and prefix syntax.. You can allow both, only standard or only prefix syntax (e.g., "ListControl.Add").
  • Versions 24 and later
    Indicate when the Business logic and UI code are mixed: If this option is checked, business code and UI code mixing errors will be enabled on all project elements.
    Remark: It is recommended to use this option on individual elements before using it on the entire project. For more details, see Splitting Business logic / UI code.
    New in version 24
    Indicate when the Business logic and UI code are mixed: If this option is checked, business code and UI code mixing errors will be enabled on all project elements.
    Remark: It is recommended to use this option on individual elements before using it on the entire project. For more details, see Splitting Business logic / UI code.
    Indicate when the Business logic and UI code are mixed: If this option is checked, business code and UI code mixing errors will be enabled on all project elements.
    Remark: It is recommended to use this option on individual elements before using it on the entire project. For more details, see Splitting Business logic / UI code.
  • Indicate the WLanguage functions kept for compatibility: If this option is checked, the WLanguage functions kept for backward compatibility are indicated in the programming standard errors (TreeSort_55 for example).
    Reminder: The functions kept for backward compatibility may not be supported anymore in a forthcoming version. It is recommended to use the corresponding new function.
These options can be overloaded for the internal components, windows and reports. See "Programming standard errors" for more details.
New in version 23

Programming standard

These options are used to define a programming standard. The programming standard "errors" signal the code lines that do not respect this standard. These errors are displayed in the "Compilation errors" pane.
The available options are:
  • Versions 26 and later
    Standard or prefix syntax: This option allows or disallows the use of standard and prefix syntax.. You can allow both, only standard or only prefix syntax (e.g., "ListControl.Add").
    New in version 26
    Standard or prefix syntax: This option allows or disallows the use of standard and prefix syntax.. You can allow both, only standard or only prefix syntax (e.g., "ListControl.Add").
    Standard or prefix syntax: This option allows or disallows the use of standard and prefix syntax.. You can allow both, only standard or only prefix syntax (e.g., "ListControl.Add").
  • Versions 24 and later
    Indicate when the Business logic and UI code are mixed: If this option is checked, business code and UI code mixing errors will be enabled on all project elements.
    Remark: It is recommended to use this option on individual elements before using it on the entire project. For more details, see Splitting Business logic / UI code.
    New in version 24
    Indicate when the Business logic and UI code are mixed: If this option is checked, business code and UI code mixing errors will be enabled on all project elements.
    Remark: It is recommended to use this option on individual elements before using it on the entire project. For more details, see Splitting Business logic / UI code.
    Indicate when the Business logic and UI code are mixed: If this option is checked, business code and UI code mixing errors will be enabled on all project elements.
    Remark: It is recommended to use this option on individual elements before using it on the entire project. For more details, see Splitting Business logic / UI code.
  • Indicate the WLanguage functions kept for compatibility: If this option is checked, the WLanguage functions kept for backward compatibility are indicated in the programming standard errors (TreeSort_55 for example).
    Reminder: The functions kept for backward compatibility may not be supported anymore in a forthcoming version. It is recommended to use the corresponding new function.
These options can be overloaded for the internal components, windows and reports. See "Programming standard errors" for more details.

Programming standard

These options are used to define a programming standard. The programming standard "errors" signal the code lines that do not respect this standard. These errors are displayed in the "Compilation errors" pane.
The available options are:
  • Versions 26 and later
    Standard or prefix syntax: This option allows or disallows the use of standard and prefix syntax.. You can allow both, only standard or only prefix syntax (e.g., "ListControl.Add").
    New in version 26
    Standard or prefix syntax: This option allows or disallows the use of standard and prefix syntax.. You can allow both, only standard or only prefix syntax (e.g., "ListControl.Add").
    Standard or prefix syntax: This option allows or disallows the use of standard and prefix syntax.. You can allow both, only standard or only prefix syntax (e.g., "ListControl.Add").
  • Versions 24 and later
    Indicate when the Business logic and UI code are mixed: If this option is checked, business code and UI code mixing errors will be enabled on all project elements.
    Remark: It is recommended to use this option on individual elements before using it on the entire project. For more details, see Splitting Business logic / UI code.
    New in version 24
    Indicate when the Business logic and UI code are mixed: If this option is checked, business code and UI code mixing errors will be enabled on all project elements.
    Remark: It is recommended to use this option on individual elements before using it on the entire project. For more details, see Splitting Business logic / UI code.
    Indicate when the Business logic and UI code are mixed: If this option is checked, business code and UI code mixing errors will be enabled on all project elements.
    Remark: It is recommended to use this option on individual elements before using it on the entire project. For more details, see Splitting Business logic / UI code.
  • Indicate the WLanguage functions kept for compatibility: If this option is checked, the WLanguage functions kept for backward compatibility are indicated in the programming standard errors (TreeSort_55 for example).
    Reminder: The functions kept for backward compatibility may not be supported anymore in a forthcoming version. It is recommended to use the corresponding new function.
These options can be overloaded for the internal components, windows and reports. See "Programming standard errors" for more details.

Compilation options

The available compilation options are as follows:
  • Compilation error on unknown identifiers: Used to define whether a compilation derror is displayed when the compiler encounters an unknown identifier (window name, control name, ...).
  • Versions 21 and later
    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.
    New in version 21
    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.
    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.
  • Versions 18 and later
    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 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.
    New in version 18
    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 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.
    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 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.
  • Versions 22 and later
    Allow "[% %]" in strings: 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: if this option is used, the code may have to be modified for some 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")
    New in version 22
    Allow "[% %]" in strings: 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: if this option is used, the code may have to be modified for some 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")
    Allow "[% %]" in strings: 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: if this option is used, the code may have to be modified for some 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")
  • Classes: optional ":" and "::" prefixes for accessing the members and the 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.
  • Versions 18 and later
    Classes: the 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.
    New in version 18
    Classes: the 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.
    Classes: the 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.
  • Versions 18 and later
    Arrays: The assignment copies the content
    When this option is enabled, the arrays are local by default, which means that the '=' operator performs a copy of the array.
    The "dynamic" keyword is used to keep the taking of reference to the assignment.
    New in version 18
    Arrays: The assignment copies the content
    When this option is enabled, the arrays are local by default, which means that the '=' operator performs a copy of the array.
    The "dynamic" keyword is used to keep the taking of reference to the assignment.
    Arrays: The assignment copies the content
    When this option is enabled, the arrays are local by default, which means that the '=' operator performs a copy of the array.
    The "dynamic" keyword is used to keep the taking of reference to the assignment.
  • Versions 21 and later
    Arrays: protected access to the elements passed to a procedure as parameter
    This option is used to protect an array element passed to a procedure as parameter. This allows you to modify, delete or add elements into the array from this procedure.
    Remark: If this option is selected, the accesses to the array may be slowed down.
    New in version 21
    Arrays: protected access to the elements passed to a procedure as parameter
    This option is used to protect an array element passed to a procedure as parameter. This allows you to modify, delete or add elements into the array from this procedure.
    Remark: If this option is selected, the accesses to the array may be slowed down.
    Arrays: protected access to the elements passed to a procedure as parameter
    This option is used to protect an array element passed to a procedure as parameter. This allows you to modify, delete or add elements into the array from this procedure.
    Remark: If this option is selected, the accesses to the array may be slowed down.
  • "Naming of data sources":
    • "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. Caution: the quotes must be deleted to handle the data source. You must not write:
      M1 is Data Source
      HReadFirst("M1")
      but
      M1 is Data Source
      HReadFirst(M1)
    • Versions 24 and later
      "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.
      New in version 24
      "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.
      "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.

      PHP The "Automatic name with references" option is not available.
Minimum version required
  • Version 10
This page is also available for…
Comments
Click [Add] to post a comment