PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
New WINDEV, WEBDEV, WINDEV Mobile 23 feature!
  • Overview
  • How to proceed?
  • Enabling the programming standard error
  • Fixing a programming standard error
  • Overloading a programming standard error
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
Programming standard errors
Overview
The programming standard errors inform you of possible detected problems whenever saving windows, pages, reports or whenever recompiling the project:
  • Functions kept for backward compatibility.
  • Access to HFSQL from the interface.
  • Using WLanguage object functions.
By default, the programming standard errors are not enabled for each new created project.
How to proceed?

Enabling the programming standard error

The programming standard errors can be enabled:
  • from the project description.
  • from the pane of compilation errors.
To enable the programming standard errors from the project description:
  1. Display the description window of project (on the "Project" pane, in the "Project" group, click "Description").
  2. In the "Compilation" tab, in the "Programming standard" section, check the requested options:
    Programming standard
    • Signal 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. We recommend that you use the corresponding new function.
    • Signal the accesses to HFSQL from windows, pages and reports: If this option is checked, all accesses to HFSQL data files are signaled in the programming standard errors.
      This option is used to quickly isolate the accesses to the database. Indeed, in some programming architectures, the accesses to the database must not be performed from the interface. These accesses must be performed in the business code from procedures or classes.
    • Signal the uses of object syntax ("ListControl.Add" for example): If this option is checked, all uses of WLanguage object syntax, available since version 23, will be signaled in the programming standard errors. This allows you to easily find the uses of this syntax if it is not allowed in the project.
  3. Validate.
To display the programming standard errors from the pane of compilation errors:
  1. Display the pane of compilation errors: on the "Home" pane, in the "Environment" group, expand "Panes" and select "Compilation errors".
  2. Click Programming standard error .
The programming standard errors are checked:
  • whenever saving a window, a page or a report.
  • whenever recompiling the project.

Fixing a programming standard error

The programming standard errors are listed in the pane of compilation errors.
To fix the programming standard errors:
  1. Double-click the error displayed in the pane. The element containing the control or the code where the problem occurs is opened in the editor. The description of relevant control is displayed.
  2. Fix the problem.

Overloading a programming standard error

By default, the programming standard defined for the project options is applied to all project elements. However, you have the ability to overload this standard for each element (window, report, page, internal component).
To overload the programming standard of a window or page:
  1. Display the description window of element.
  2. In the "Details" tab, click the "Programming standard" button.
    Programming standard for a window
    Programming standard for a window
  3. In the window that is displayed, select the process mode of each option:
    Overloading a programming standard error (window or page)
    • Like the project: the programming standard that is applied is the project one.
    • Signal: the programming standard is always applied for this element.
    • Don't signal: the programming standard is never applied for this element.
  4. Validate the programming standard window.
  5. Validate the window description.
To overload the programming standard of a report:
  1. Display the description window of report.
  2. In the "Options" tab, click the "Programming standard" button.
  3. In the window that is displayed, select the process mode of each option:
    Overloading a programming standard error (report)
    • Like the project: the programming standard that is applied is the project one.
    • Signal: the programming standard is always applied for this element.
    • Don't signal: the programming standard is never applied for this element.
  4. Validate the programming standard window.
  5. Validate the report description.
To overload the programming standard of an internal component:
  1. Display the description window of internal window ("Description" option of internal component displayed in the project explorer).
  2. In the "Compilation" tab, specify the options of programming standard that will be overloaded:
    • Like the project: the programming standard that is applied is the project one.
    • Signal: the programming standard is always applied for this element.
    • Don't signal: the programming standard is never applied for this element.
  3. Validate the description of internal component.
Minimum required version
  • Version 23
This page is also available for…
Comments
Click [Add] to post a comment